Mobile alerting network

ABSTRACT

A system for providing a mobile application includes a Mobile Subscriber Detection Authorization and Verification System (MSDAVS), to request and receive confidential information from a confidential information owner relating to a user who opted-in to a mobile service application, and to communicate the received confidential information to a mobile application service provider. The MSDAVS can include an opt-in database, to store opt-in or registration data of the opted-in users of the mobile service application and a service policy database. The mobile application service can be a mobile traffic alerting service, the confidential information owner a telephone number database of one of a wireless carrier or a telephone number database operator, and the requested confidential information a list telephone numbers of opted-in users in an alert area, defined by the mobile traffic alerting service.

RELATED APPLICATIONS

The present application is a continuation of application Ser. No.12/402,286, filed Mar. 11, 2009 entitled MOBILE ALERTING NETWORK, whichis a continuation-in-part of application Ser. No. 12/251,155, filed Oct.14, 2008, entitled MOBILE ALERTING NETWORK, which is acontinuation-in-part of application Ser. No. 11/970,922 filed Jan. 8,2008, entitled PASSIVE TRAFFIC ALERT AND COMMUNICATION SYSTEM, both ofwhich are hereby incorporated by reference in their entirety.

BACKGROUND

1. Field of Invention

The present invention relates to mobile alerting systems, more preciselyto location based alerting systems related to traffic and promotionalcontent.

2. Description of Related Art

With great progress on every front of telecommunications, many new typesof uses of these technologies emerge. One thrust of evolution involvesproviding traffic information more efficiently. At this time, trafficinformation is gathered in a somewhat disorganized manner. It is alsorelayed through inefficient channels.

Presently, the traffic information is often gathered from policereports, or the traffic helicopters of news channels, or road-sidesensors. However, after an initial announcement of an overturned truckblocking traffic, the police may fail to inform the news channels thatthe overturned truck has been removed. Or the road side sensors may notappreciate that a lack of “slow car speed” signals does not necessarilyindicate an “all clear” traffic condition. Famously, when the 35W bridgecollapsed in Minneapolis in 2007, the roadside sensors signaled “normaltraffic” several hours after the bridge collapse and total paralysis ofthe Minneapolis traffic. Thus, presently used traffic information may beoutdated or incorrectly interpreted in some systems. Therefore, currentmethods of reporting traffic information are not necessarily reliableand leave room for improvements.

Further, the present methods of broadcasting traffic information arequite ineffective as well. In a larger metropolitan area news channelstypically broadcast a long traffic report, which may list many trafficdelays, accident and other problems all over the metropolitan area.However, most of these reports are not relevant for any particulardriver on a particular road, forcing most users of this service to beexposed to unnecessarily long announcements. Worse yet, driversinundated with a long report of traffic problems may get numbed and missthe one report which was relevant for their commute.

Various electronic service providers now offer devices which delivermore personalized traffic information. However, in many cases the driverhas to enter e.g. on a webpage or into the device itself the specificroute he or she is going to take, or store in a memory his/her typicalcommute route. In return, the service provides the road conditions onlyfor the entered or stored roads. Thus, if e.g. a driver takes a lesscustomary road on a given day and forgot to enter his choice, theprovided traffic information is less useful. Further, the serviceprovides the overall traffic information, not the one relevant for theparticular location of the driver on the road, such as a convenient exitto take, or what is the expected time delay given the driver's location.

Also, many of these services require the driver to actively manipulatethe device, e.g. launch an application on a cell phone. This requirementis problematic, as an increasing number of states and countries nowrequire that the driver shall not divert his or her attention fromdriving by e.g. banning manual handling of cell phones. And even if adriver is prepared to launch an application, this interrupts thefunction presently carried out by the cell phone, such as theconversation the driver was having. Finally, many of these services arefee based—another inconvenience.

All of the aspects of present traffic delivery systems, described above,define areas where improvements are called for.

SUMMARY

Briefly and generally, a new passive traffic alerting method may includethe steps of: identifying traffic events from analyzing trafficinformation; selecting an identified traffic event based on a locationrelated to a mobile communicator; and alerting the mobile communicatorwith a passive message regarding the selected traffic event withoutprompting the mobile communicator to launch an application on a mobilecommunication device.

Some embodiments include the steps of: identifying traffic events fromanalyzing traffic information; selecting an identified traffic eventbased on a location related to a mobile communicator; and alerting themobile communicator with a passive message regarding the selectedtraffic event without prompting the mobile communicator to launch anapplication on a mobile communication device.

Some embodiments include the steps of: identifying traffic events fromanalyzing traffic information; selecting a user-zone based on a locationrelated to a mobile communicator; selecting an identified traffic eventbased on a relation of identified traffic events and the user-zone; andalerting the mobile communicator with a passive message regarding theselected traffic event.

Some embodiments include the steps of: identifying traffic events fromanalyzing traffic information; selecting an identified traffic eventbased on a location related to a mobile communicator; and alerting themobile communicator regarding the selected traffic event with aplurality of messages in a hierarchical manner.

Some embodiments include the steps of: determining an alert zone byrating a traffic incident and overlaying a map of the incident, a map ofcell-phone towers, and a map of a corresponding road network; acquiringuser identification of cell phone users from data from cell-phone towersin the alert-zone; identifying subscribers from acquired cell-phonetower data; matching subscribers with appropriate alerts; sendingappropriate alert messages to cell phones of identified subscribers.

Some embodiments include the steps of: receiving traffic alertinformation and start composing an alert message in response; composingalert message; compiling alert message in different formats; routingdifferently formatted alert messages to subscribers expecting thatformat; sending the routed alert messages to the correspondingsubscribers through matching gateways of a service provider and acell-phone carrier.

Some embodiments include a Mobile Alert Network service and system. TheMobile Alert Network (MAN) service can include identifying an Alert Arearelated to an Event Location, identifying a group of subscribers in theAlert Area, and broadcasting an Alert Message to the identifiedsubscribers in a push-to-talk-equivalent (PTTE) environment.

The event can be any one of a wide variety of events, including atraffic accident, a weather alert, a recreational or sports event, or anE911 emergency situation, e.g. a chemical or hazardous material spill,possibly threatening with a health hazard.

The subscribers can be identified by their subscriber mobile ID, or bytheir International Mobile Equipment Identity (IMEI), or by any otherhandset identification information, such as an IMSI or MIN number, or bytheir phone number.

An Alert Message can be prepared and broadcast to the identifiedsubscribers by a master broadcaster. The master broadcaster can be aBroadcast Module of a server of the MAN Service. The Alert Message caninclude a Short Message System (SMS) message. The MAN Service can beprovided instead of, or in parallel to the regular SMS Aggregators.

The Alert Messages can contain three parts. Part 1 can alert thesubscribers and inform them about the cause of alert, such as anaccident or any other event. Part 2 can offer Alert Message relatedchoices, such as receiving the Alert Message in audio. Part 3 may offerevent related choices, such as receiving promotional information oroffers in relation to the event, such as in the proximity of the event.

The MAN Service may include an Alert Information Service, generating anAlert Information in relation to the Event. The MAN Service can alsoinclude a Subscriber Selector, locating and identifying subscribers ofthe MAN service, in relation to the identified Event, such assubscribers in the proximity of a traffic accident.

The Subscriber Selector may contact a Broadcast Module with the AlertInformation and the list of Identified Subscribers. The Broadcast Modulemay generate and assemble an Alert Message in response to thecommunication from the Alert Information Service and the SubscriberSelector.

The Event related choices in Part 3 of the Alert Message may begenerated based on campaigns by Promotional Agents, who could be ofinterest for the mobile communicator.

The Alert Message can be then broadcast by the Broadcast Module to AlertClients which have been downloaded onto the subscriber's handsets. TheAlert Message can be broadcast through one or more Carrier Networks.

The Alert Message can contain an SMS with the following components:date, time, message ID, size, and hot key number.

In some implementations a Wrapper is downloaded on the handsets as apart of the Alert Client. The functions of the Wrapper may include:managing Alert Messages, managing a mailbox function, includingprioritizing messages, downloading and updating applications, managingsubscriptions, storing data, related to messages and promotions, andpersonalizing.

The Wrapper can update the on-board application to a level required bythe operation of the handset, such as by the requirement of downloadingand properly displaying of a multimedia message

Some implementations include a Logger application to provide a detailedaccount of the operation of the handset and its user. The Logger mayrecord and report that the transmission of the Alert Message has beencompleted, the time when the transmission of the Alert Message wascompleted, whether the subscriber actually requested, or pulled theavailable promotional material, and whether the subscriber placed anactual order in response to the promotional message.

Some implementations can include a web-based Campaign Interface. AParticipating Vendor may use such a Campaign Interface to publishvarious campaign items.

Using the Campaign Interface, the Participating Vendor may specify thetype of Alert Messages, the details of the Promotional Offer, thelocation aspects of the Promotional Offer, and other logistics of thecampaign, such as the duration of the Offer.

The Campaign Interface may also include a module for the BillingArrangements and a Reporting Module to provide feedback to the PromotionAgents and Vendors about the progress of the campaign.

The above functions can be facilitated and managed by the MAN SystemManager, deployed on MAN servers. The MAN System Manager may include: anAlert Information Manager, a Subscriber Manager, a Broadcast Manager, aPromotion Agent Manager, a Carrier Manager, an SMS Aggregator Manager,an Alert Client Manager, and a Billing Manager.

Implementations also include a Sensor Array-based Mobile Broadcast Alert(SAMBA) Service and corresponding SAMBA System. The SAMBA System andManagers can operate analogously to the MAN System and Managers. Some ofthe differences between the SAMBA and the MAN systems include that theSubscriber Manager in the SAMBA System may locate and identifysubscribers using a specialized Sensor Array. The Sensor Array maycontain a large number of sensors, whose functionalities includereceiving self-identification information, broadcast by the cell phones;determining the location of the cell phones using e.g. triangulation ofthese self-identification signals; and correlating the location and theidentification information.

In some implementations, establishing the identity of the cell phone andthe corresponding user may require cooperation between the Sensor Arrayand the SAMBA Central Servers.

Cell phones relay some of their identification information regularly, sothat the Carrier Networks can locate them when an incoming call istrying to reach the phone. This identification information may includethe mobile ID, the International Mobile Equipment Identity (IMEI), orany other handset identification information, such as an IMSI or MIN. Insome cases this identification information can be a GPS information,which can then be used to establish the MIN (Mobile IdentificationNumber) of the phone number of the handset. In some cases theidentification information can be any combination of the above.

In principle the triangulation or GPS information can determine theprecise location of the cell phone and the broadcast identificationinformation can determine the identity of the cell phone and its user.This information is typically sufficient for the operation of the restof the SAMBA system, such as sending out Alert Messages and promotionsto the SAMBA subscribers among the localized and identified users.

A SAMBA Operation Display can display the location of the subscribers,and possibly some of their personal identifiers, which can include theIMEI, IMSI, MIN or other handset identification information, as well aspersonal information.

In order to verify the identity of two phones which are closer than theresolution of the Sensor Array, implementations of the SAMBA system mayinclude verification cycles to determine the proper identification ofthe handsets and their users.

An embodiment of an Identification—Verification Cycle may include: newpatrons can be given invitations to subscribe/enroll to the SAMBAService. When the patrons enroll into the SAMBA Service by e.g. textinga message, the Sensor Array can pick up this message and extract theIMEI, IMSI, MIN or other handset identification information of theenrolling patron.

Further, in response to the text message, the patron maybe invited toopt in into the SAMBA Service, having been informed about the trackingfeatures of the SAMBA service. The patron may opt in into the SAMBAService, e.g. by texting “yes” to an address.

Next, an Alert Client may be downloaded onto the patron's handset. TheAlert Client may report to the SAMBA servers the phone number or anyother identification information of the patron. This information can beused to verify the identity of a cell phone.

In some embodiments of the SAMBA Operation Display, different classes orgroups of users can be indicated by different symbols.

In some implementations a system for providing a mobile applicationincludes a Mobile Subscriber Detection Authorization and VerificationSystem (MSDAVS), configured to request and receive confidentialinformation from a confidential information owner relating to a user whoopted-in to a mobile service application, and to communicate thereceived confidential information to a mobile application serviceprovider (MASP).

In some implementations the MSDAVS includes an opt-in database, to storeopt-in or registration data of the opted-in users of the mobile serviceapplication.

In some implementations the MSDAVS includes a service policy database,to store policy data regarding the mobile application service.

In some implementations the confidential information owner is one of awireless carrier, a financial record manager, a gaming informationmanager, and an educational information manager.

In some implementations the mobile application service provider is oneof a mobile traffic alert network, a location based service, a mobileapplication, a mobile financial application, a mobile educationalapplication and a mobile gaming application.

In some implementations the mobile application service is a mobiletraffic alerting service, the confidential information owner is atelephone number database of one of a wireless carrier or a telephonenumber database operator, and the requested confidential information isa list telephone numbers of opted-in users in an alert area, defined bythe mobile traffic alerting service.

In some implementations the alert area is defined by the mobile serviceprovider by identifying the corresponding alert area cell towers, andthe list of phone numbers is generated by compiling the list of allphone numbers, registered at the alert area cell towers.

In some implementations the MSDAVS is configured to acquire a list ofcell towers in the alert area from a cell tower database, to forward thelist of alert area cell towers to a telephone number database, and toreceive a list of telephone numbers registered at the cell towers fromthe telephone number database.

In some implementations the MSDAVS is configured to communicate thereceived list of telephone numbers in the alert area to an opt-indatabase, to cause the opt-in database to cross reference the list oftelephone numbers with a list of opted-in users to create a list oftelephone numbers of the opted-in users in the alert area, to receivefrom the opt-in database the list of telephone numbers of the opted-inusers in the alert area.

In some implementations the MSDAVS is configured to receive a list ofvirtual telephone numbers registered at alert area cell towers, toforward the received list to a telephone number database, and to receivea list of mobile equipment identifiers and corresponding virtualtelephone numbers from the telephone number database, created by thetelephone number database based on the list of virtual telephonenumbers.

In some implementations the MSDAVS is configured to communicate the listof mobile equipment identifiers and corresponding virtual telephonenumbers to the opt-in database for cross-referencing, to receive a listof virtual telephone numbers of opted-in users in the alert area,created through cross-referencing by the opt-in database, and tocommunicate the list of virtual telephone numbers of opted-in users inthe alert area to the provider of the mobile traffic alerting service.

In some implementations the mobile application service is a sensorarray-based mobile broadcast alerting (SAMBA) service, the confidentialinformation owner is a telephone number database of one of a wirelesscarrier or a telephone number database operator, and the requestedconfidential information is a list telephone numbers of opted-in usersin a SAMBA operation area.

In some implementations the list of phone numbers is generated bycompiling the list of phone numbers, sensed by sensors in the SAMBAoperation area.

In some implementations the MSDAVS is configured to communicate thereceived list of telephone numbers to an opt-in database, to cause theopt-in database to cross reference the list of telephone numbers with alist of opted-in users to create a list of the telephone number of theopted-in users in the SAMBA operation area, and to receive from theopt-in database the list of the telephone numbers of the opted-in usersin the SAMBA operation area.

In some implementations the MSDAVS is configured to receive a list ofvirtual telephone numbers sensed by SAMBA sensors, to forward thereceived list to a telephone number database, and to receive a list ofmobile equipment identifiers and corresponding virtual telephone numbersfrom the telephone number database, created by the telephone numberdatabase based on the list of virtual telephone numbers.

In some implementations the MSDAVS is configured to communicate the listof mobile equipment identifiers and corresponding virtual telephonenumbers to the opt-in database for cross-referencing, to receive a listof virtual telephone numbers of opted-in users in the SAMA operationarea, created through cross-referencing by the opt-in database, andcommunicating the list of virtual telephone numbers of opted-in users inthe SAMBA operation area to the provider of the SAMBA service.

In some implementations a method of operating a Mobile SubscriberDetection Authorization and Verification System includes requestingconfidential information from a confidential information owner inconnection to providing a mobile application service to an opted-inuser, receiving the requested confidential information, and relaying theconfidential information to a provider of the mobile applicationservice.

In some implementations the method includes receiving an opt-in messagefrom a user to opt-in to the mobile application service, and storing atleast a portion of the opt-in message in an opt-in database.

In some implementations the method includes requesting service policyinformation regarding the opted-in mobile application service from aservice description database, and receiving a response regarding servicepolicy in connection to the opted-in mobile application service from theservice description database.

In some implementations the method includes forwarding at least aportion of the opt-in message to a provider of the mobile applicationservice, and receiving a request from the provider of the mobileapplication service for the confidential information.

In some implementations the mobile application service is a mobiletraffic alerting service, the confidential information owner is atelephone number database of one of a wireless carrier or a telephonenumber database operator, and the requested confidential information isa list telephone numbers of opted-in users in the alert area, defined bythe mobile traffic alerting service.

In some implementations the alert area is defined by the mobile serviceprovider by identifying the corresponding alert area cell towers, andthe list of phone numbers is generated by producing the list of phonenumbers, registered at the alert area cell towers.

In some implementations the method includes acquiring a list of celltowers in the alert area from a cell tower database, forwarding the listof alert area cell towers to a telephone number database, and receivinga list of all telephone numbers registered at the cell towers from thetelephone number database.

In some implementations the method includes communicating the receivedlist of telephone numbers in the alert area to an opt-in database,causing the opt-in database to cross reference the list of phone numberswith a list of opted-in users to create a list of opted-in users in thealert area, and receiving from the opt-in database the list of telephonenumbers of the opted-in users in the alert area.

In some implementations the method includes receiving a list of virtualtelephone numbers registered at alert area cell towers, forwarding thereceived list to a telephone number database, and receiving a list ofmobile equipment identifiers and corresponding virtual telephone numbersfrom the telephone number database, created by the telephone numberdatabase based on the list of virtual telephone numbers.

In some implementations the method includes communicating the list ofmobile equipment identifiers and corresponding virtual telephone numbersto the opt-in database for cross-referencing, receiving a list ofvirtual telephone numbers of opted-in users in the alert area, createdthrough cross-referencing by the opt-in database, and communicating thelist of virtual telephone numbers of opted-in users in the alert area tothe provider of the mobile traffic alerting service.

In some implementations the mobile application service is a sensorarray-based mobile broadcast alerting (SAMBA) service, the confidentialinformation owner is a telephone number database of one of a wirelesscarrier or a telephone number database operator, and the requestedconfidential information is a list of telephone numbers of opted-inusers in a SAMBA operation area.

In some implementations the list of phone numbers is generated bycompiling the list of phone numbers, sensed by sensors in the SAMBAoperation area.

In some implementations the method includes communicating the receivedlist of telephone numbers to an opt-in database, causing the opt-indatabase to cross reference the list of phone numbers with a list ofopted-in users to create a list of telephone numbers of the opted-inusers in the SAMBA operation area, and receiving from the opt-indatabase the list of the telephone numbers of the opted-in users in theSAMBA operation area.

In some implementations the method includes receiving a list of virtualtelephone numbers sensed by SAMBA sensors, forwarding the received listto a telephone number database, and receiving a list of mobile equipmentidentifiers and corresponding virtual telephone numbers from thetelephone number database, created by the telephone number databasebased on the list of virtual telephone numbers.

In some implementations the method includes communicating the list ofmobile equipment identifiers and corresponding virtual telephone numbersto the opt-in database for cross-referencing, receiving a list ofvirtual telephone numbers of opted-in users in the SAMBA operation area,created through cross-referencing by the opt-in database, andcommunicating the list of virtual telephone numbers of opted-in users inthe SAMBA operation area to the provider of the SAMBA service.

In some implementations a system for providing a mobile applicationincludes a mobile application service provider (MASP), configured torequest a Mobile Subscriber Detection Authorization and VerificationSystem (MSDAVS) to request and receive confidential information from aconfidential information owner in connection to providing the mobileapplication service to opted-in users, and to provide the mobileapplication service to the opted-in users upon the receipt of theconfidential information.

In some implementations the MSDAVS includes an opt-in database, to storeopt-in or registration data of the opted-in users of the mobileapplication service.

In some implementations the MSDAVS includes a service policy database,to store policy data regarding the mobile application service.

In some implementations the confidential information owner is one of awireless carrier, a financial record manager, a gaming informationmanager, a mobile service information manager, and an educationalinformation manager.

In some implementations the mobile application service provider is oneof a mobile traffic alert network, a location based service, a mobileinformation service application, a mobile financial application, amobile educational application and a mobile gaming application.

In some implementations the mobile application service is a mobiletraffic alerting service, the confidential information owner is atelephone number database of one of a wireless carrier or a telephonenumber database operator, and the requested confidential information isa list telephone numbers of opted-in users in an alert area, defined bythe mobile traffic alerting service.

In some implementations the alert area is defined by the mobile serviceprovider by identifying the corresponding alert area cell towers, andthe list of phone numbers is generated by producing the list of phonenumbers, registered at the alert area cell towers.

In some implementations the MSDAVS is configured to receive from theMSDAVS the list of telephone numbers of opted-in users in the alertarea, and to provide the mobile traffic alerting service to the opted-inusers in the alert area.

In some implementations the mobile application service is a sensorarray-based mobile broadcast alerting (SAMBA) service, the confidentialinformation owner is a telephone number database of one of a wirelesscarrier or a telephone number database operator, and the requestedconfidential information is a list telephone numbers of opted-in usersin a SAMBA operation area.

In some implementations the list of phone numbers is generated bycompiling the list of phone numbers, sensed by sensors in the SAMBAoperation area.

In some implementations the SAMBA service provider is configured toreceive the list of opted-in users in the SAMBA operation area from theMSDAVS, and to provide the SAMBA service to the opted-in users in theSAMBA operation area.

In some implementations a method of providing a mobile applicationservice includes directing a Mobile Subscriber Detection Authorizationand Verification System (MSDAVS) to request confidential informationfrom a confidential information owner to assist the providing of themobile application service to opted-in users, receiving the confidentialinformation, acquired by the MSDAVS from the confidential informationowner, and providing the mobile application service to the opted-inuser.

In some implementations a mobile community notification system includesa Mobile Subscriber Detection Authorization and Verification System(MSDAVS), configured to request and receive confidential informationfrom a confidential information owner related to a notification area,and to communicate the received confidential information to a mobilecommunity notification service (MCNS) provider.

In some implementations the confidential information owner is atelephone number database of one of a wireless carrier or a telephonenumber database operator, and the requested confidential information isa list telephone numbers of users in the notification area.

In some implementations the notification area is defined by the mobilecommunity notification service provider by identifying the correspondingnotification area cell towers, and the list of phone numbers isgenerated by compiling the list of phone numbers, registered at thenotification area cell towers.

In some implementations the MSDAVS is configured to acquire a list ofcell towers in the notification area from a cell tower database, toforward the list of notification area cell towers to a telephone numberdatabase, and to receive a list of telephone numbers registered at thecell towers from the telephone number database.

In some implementations the MSDAVS is configured to receive a list ofvirtual telephone numbers registered at alert area cell towers, toforward the received list to a telephone number database, and to receivea list of mobile equipment identifiers and corresponding virtualtelephone numbers from the telephone number database, created by thetelephone number database based on the list of virtual telephonenumbers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates the steps 110-130 of passive traffic alerting method100.

FIG. 2 illustrates the sub-steps 111-113 of the identifying andanalyzing step 110.

FIG. 3 illustrates the sub-steps 121-125 of the selecting a trafficevent step 120.

FIG. 4 illustrates the sub-steps 122-123 of user-zone selecting sub-step121.

FIGS. 5A-N and 5P illustrate various situations and embodimentsinvolving the user-zone, the event-zone and the traffic-event.

FIG. 6. illustrates the steps 131-132 of generating sponsored alertmessages step 130.

FIG. 7 illustrates a hierarchy of alert messages 133-135.

FIG. 8 illustrates a multi-level messaging embodiment.

FIG. 9 illustrates an alternative embodiment 200.

FIG. 10 illustrates another alternative embodiment 300.

FIG. 11 illustrates an alert message generation method 400.

FIG. 12 illustrates an embodiment of the alert message transferprotocol.

FIG. 13 illustrates an embodiment of the alert message generation method500.

FIG. 14 illustrates an embodiment of a MAN Service 1000.

FIGS. 15A-B illustrate embodiments of a MAN System.

FIGS. 16A-B illustrate an Alert Message 1301.

FIG. 17 illustrates a MAN system 1400.

FIG. 18 illustrates a MAN system.

FIG. 19 illustrates a Wrapper 1500.

FIG. 20 illustrates an updating function of the Wrapper.

FIG. 21 illustrates a Logger 1600.

FIG. 22 illustrates an Alert Client 1700.

FIG. 23 illustrates a Campaign Interface 1800.

FIG. 24 illustrates a MAN System Manager 1900.

FIG. 25 illustrates a SAMBA system 2400.

FIG. 26 illustrates a SAMBA System Manager 2900.

FIG. 27 illustrates a Sensor Array.

FIG. 28 illustrates a Sensor Array Operation 2500.

FIG. 29 illustrates a SAMBA Operation Display 2600.

FIG. 30 illustrates an Identification and Verification Cycle 2700.

FIG. 31 illustrates a MSDAVS system.

FIGS. 32A-B illustrate a MSDAVS system with different opt-in procedures.

FIG. 33 illustrates the regular operation of a MSDAVS system.

FIG. 34 illustrates the movement of the various phone numbers in anembodiment of the MSDAVS system.

FIG. 35 illustrates a Traffic-MSDAVS MAN system.

FIG. 36 illustrates a Traffic MSDAVS MAN System Manager.

FIG. 37 illustrates a SAMBA-MSDAVS system.

FIG. 38 illustrates a Mobile Community Notification System.

DETAILED DESCRIPTION

FIG. 1 illustrates a passive traffic alerting method 100. The passivealerting method 100 can include: identifying traffic events fromanalyzing traffic information (step 110); selecting an identifiedtraffic event based on a location related to a mobile communicator (step120), and alerting the mobile communicator with a passive messageregarding the selected traffic event without prompting the mobilecommunicator to launch an application on a mobile communication device(step 130).

FIG. 2 illustrates that step 110 may include collecting trafficinformation from a plurality of traffic data sources (step 111) andidentifying a traffic event by integrating collected traffic information(step 113). Step 113 may include identifying an accident, a trafficslow-down, a traffic-jam, a road-construction, and a traffic condition.Besides typical accidents, such traffic events can be caused e.g. by asporting event, an entertainment event, a weather event, or a trafficcontrol event. Typical examples include a sudden downpour causingslippery roads, leading to an accident involving several vehicles. Suchan accident can give rise to extensive delays. Other examples include aconcert or a sporting event, where the large number of vehiclesconverging on the same location causes major delays without anyaccident. Note that the inverse of the above cases can also be anoteworthy traffic event: e.g. the removal of an overturned truck, orthe opening of an exit which was under construction up to the opening.

A common aspect of these traffic events is the change in the speed oftraffic, typically a slow-down. Traffic data providers developeddifferent technologies to recognize, identify and track such slow-downof the traffic. Sources of such traffic data include: the police,issuing police reports on an accident; news organizations, operatinghelicopters and reporting over broadcast systems (e.g. a TV stationoperating its own traffic chopper and broadcasting its report live);mobile telephone companies, who acquire information about the speed ofvehicles by tracking how quickly mobile phone signals move fromcell-phone tower to cell-phone tower; various trafficreporting/controlling agencies, who e.g. deploy a large network ofsensors into the road surface and collect the data generated by thesesensors, or deploy a large number of traffic cameras which observetraditional traffic bottlenecks; and road construction companies, whoknowingly cause traffic delays by closing a lane or an exit for repair.

Remarkably, any one of these traffic data sources can provide incompletedata. For example, a cell phone tower senses not only the vehiclespassing by on the highway but also the vehicles passing by on a nearbyresidential road. A red light stopping vehicles on this residential roadcan be falsely interpreted by the tower's unsophisticated system as asignal of a traffic-jam on the highway itself, creating a false alert.Or, sensors built into the road surface may misinterpret signals, asmentioned above in relation to a bridge collapse. Or the police/highwaypatrol may accurately announce when a truck overturned on a highway, butfail to report when the overturned truck is removed, leading tocontinued reporting of an accident which has been cleared up since.

FIG. 2 illustrates that such inefficiencies can be drastically reducedby collecting traffic information from a plurality of traffic datasources in step 111, and integrating the collected traffic informationin step 113. In an example of step 111, if a mobile phone operatorreports a slowdown of traffic from its cell-tower data, a trafficreporting organization (TRO), or a traffic service provider (TSP) mayacquire additional traffic information from a second source of trafficdata such as a live-feed from a video camera, which is pointed at thecorresponding segment of the highway. Then in step 113, the TRO mayintegrate the traffic information from the two sources by crossreferencing the cell tower data with the video camera feed to verifythat indeed an accident occurred. The integrating step 113 may involvechecking that the video camera feed corresponds to the same segment ofthe highway as the cell tower data. Or if the police do not issue an“all-clear” after an initial report of an overturned truck, a TRO mayperform step 111 by directing a news chopper to the impacted section ofthe highway and ask for additional information. Then, in step 113, theTRO may instruct the chopper to check whether the overturned truck hasbeen removed, describing in detail which segment of the highway thepolice report referred to.

Often the traffic information is complex and unusual situations andcorrelations occur. In many embodiments of the integrating step 113 thecomplex information is integrated by human intervention: an employee ofthe TRO summarizes the cell-tower data and cross references it with thevideo feed from a traffic helicopter.

In embodiments of step 111, which collect traffic information fromcell-tower data, issues of privacy may be involved. To alleviate anypotential problems, embodiments of the present method make sure thatonly anonymous information is used. For example, the actual ID of thecell phone users is not recorded or reported, only the average speed ofthe cell phone users, inferred e.g. from how quickly they move fromcell-tower to cell-tower.

In some embodiments the analysis step 110 also involves step 112: amodeling of the traffic. For example, “neural network” models, or“real-time traffic” models can be used for modeling traffic in step 112.These models can be used to generate a traffic assessment. Theseassessments include predicting what kind of traffic delays will becaused by a freshly overturned truck in 10, 20, or 30 minutes, on whattime scale will the traffic jam dissipate, and how will the changingtraffic patterns (such as motorists taking alternate routes) impactthese predictions. There are a vast number of such traffic models andusing any one of these models is understood to be within the scope ofthe step 112. In multi-level modeling embodiments, more than one methodcan be employed to generate traffic predictions and then a second levelevaluator may chose which model's prediction should be accepted as thetraffic assessment. In such embodiments the step 113 may involveintegrating traffic data acquired in step 111 with the trafficassessments, generated during the modeling step 112.

An example can be that in a step 111 a TSP is informed about a laneclosure and the TSP comes to the idea to suggest an alternate route toavoid delays. Then, a modeling step 112 is carried out to estimatewhether the idea of a no-delay alternate route is verified by modeling.The modeling instead comes to the conclusion that a 10 minute delay willbe likely caused by the excess traffic. In an additional step 111 theTSP acquires further traffic information in the form of road-embeddedsensor data to check whether the vehicle speed on the alternate route isindeed consistent with the 10 minutes delay prediction of the modeling.The acquired road sensor data, however, indicates only a 5 minutesdelay. Finally, in an embodiment of step 113, the original lane closureinformation, the modeling prediction of 10 minutes delay, and the roadsensor data, indicating only 5 minutes delay, are integrated, enablingthe TSP to identify a traffic event of the lane closure and theaccompanying 5-10 minutes delay on the alternate route. The sequence ofthese steps can be reordered, and some steps can be carried out morethan once, as in the just described embodiment.

FIG. 3 illustrates step 120, which involves selecting one of theidentified traffic events. Step 120 may start with step 121: selecting auser-zone corresponding to the mobile communicator. The user-zone can beselected for various reasons. One of these reasons is to providepersonalized traffic information. Selecting a user-zone around themobile communicator identifies which road's traffic information isneeded or requested by the mobile communicator. The user-zone can beselected by the TSP, e.g. as a default, or to represent a choice of themobile communicator. In the latter embodiment, the mobile communicatormay be prompted to choose a user-zone and then relay the choice to theTSP.

FIG. 4 illustrates that step 121 may include step 122: determining alocation of the mobile communicator from location data provided bymobile communication stations of a mobile communication network or fromdata provided by a global positioning system. Step 122 can be followedby step 123: selecting the user-zone as an area centered at the locationof the mobile communicator with a shape and extent. In someapplications, the user-zone can be a “bubble” around the mobilecommunicator: e.g. 10 mile ahead the vehicle and a half mile wide oneach side of the highway. Any other shape and extent can be specified aswell. The extent and shape of the user-zone corresponding to each cellphone can have default values. These default values can be reset on aweb-page or through a setup process during a telephone-call. It can bealso specified whether the center of the user-zones, or any otherdistinguishing coordinate, e.g. the focal point of an ellipticuser-zone, should be chosen to track the location of the mobilecommunicator. The shape and extent and any other characteristic of theuser-zone can be updated by the mobile communicator during regularoperations. In other embodiments, the shape and extent is programmed tovary according to identified traffic events by various serviceproviders.

In an example, if a mobile communicator is alerted in step 130 that aselected traffic event is ahead of him, then the mobile communicator maywish to decide which alternate route to take. For making the rightdecision the mobile communicator may desire information on whether anyof the possible alternate routes has a traffic jam on it. To deliver ananswer, the TRO or TSP may alter the user-zone to become much wider,once a traffic event in the original user-zone has been reported, sincewider user-zones prompt receiving alerts about traffic eventspotentially blocking some of the alternate routes. In anotherembodiment, the extent of the user-zones is increased as a traffic jamincreases, in order to allow the driver to take alternate routes beforegetting caught in the traffic jam. More generally, the user-zone may beincreased by the TSP so as to enable the mobile communicator to makeinformed choices in a timely manner, typically to take alternate routesor to pull over for shopping until the traffic jam dissolves.

Step 122 may include determining the location of the mobile communicatorfrom location data provided by mobile communication stations of a mobilecommunication network. The location of the mobile communicator can beextracted e.g. by a triangulation method on the data, collected from thecell phone towers. In other embodiments, the location of the mobilecommunicator can be extracted from data provided by a global positioningsystem or a related cell-phone GPS system.

The user-zone is typically moving with the vehicle of the mobilecommunicator and thus it is constantly updated. In some embodiments, thelocation of the mobile communicator is determined by at least partiallyrelying on the speed of the mobile communicator. The speed can beinferred e.g. from cell phone tower data. In some embodiments, theuser-zones of cell phone users within a section of a metropolitan areacan be tracked by a cell phone service provider in regular intervals,collecting data from cell phone towers.

In some embodiments the data about the user-zones are forwarded by thecell phone service provider to a traffic reporting organization (TRO),or to a traffic service provider (TSP), who specializes in practicingthe presently described passive alerting method 100. In theseembodiments the TRO or TSP tracks the moving user-zones. In otherembodiments, the operators of the cell phone towers or the cell phoneservice providers, or the GPS service provider tracks and updates theuser-zones.

In step 125 in FIG. 3 the TRO or TSP, or any other of the listedoperators, may select one of the identified traffic events by updatingthe moving tracked user-zones of moving mobile communicators andevaluate whether any one of the identified traffic events fall withinthe updated user-zones. Once an identified traffic event is found tofall within the user-zone of a mobile communicator, step 130 can becarried out e.g. by alerting the mobile communicator with a passivemessage about the selected traffic event.

As an example, a driver on her way home from the office may switch onher cell phone. The cell phone sends identifying signals to the celltowers. The cell phone service provider transmits information about thedriver to a traffic service provider (TSP), including her location (step122) and user-zone (step 123), which were either transmitted in theidentifying phase or stored based on previous communications. The TSPprocesses the identifying signals and extracts the location of thedriver and recalls her preprogrammed user-zone which is 8 miles ahead ofthe vehicle and half mile wide. As the driver drives on highway US 101,the TSP continuously updates the user-zone and evaluates whether thereis a traffic event within her user-zone. At some time a new trafficaccident occurs 20 miles ahead of the driver on US 101. Correspondingtraffic data is received by the TSP and is identified as an accident,causing a 20 minutes delay following the steps 111-113. This brings thepresently active traffic accidents in the greater metropolitan area to12. However, the TSP does not burden the driver with informationregarding all 12 accidents. Instead, only when the driver arrives within8 miles of the newly identified traffic accident, the TSP selects theaccident on US 101 out of the 12 active accidents. The TSP then sends apassive alert signal only to the driver whose user-zone just overlappedwith the identified traffic event that a traffic accident lies ahead,causing a 20 minutes delay. Since the driver knows that the size of heruser-zone was set to 8 miles, this alert signal lets the driver know notonly the existence of the traffic accident but its approximate distancefrom the vehicle and the probable delay caused by it.

In other embodiments, the user-zone can be selected differently. Forexample, the user-zone can be selected based on any kind of mobilecommunicator information. Embodiments include selecting a user-zonebased on an address, such as the home of the mobile communicator. Thischoice lets the mobile communicator know whether there are trafficproblems around her home, to assist her in planning the fastest routehome.

In yet other embodiments, the user-zone can be based on another person.For example, the user-zone can be defined according to the location ofthe cell phone of the mobile communicator's spouse, family member,co-worker or business partner. These embodiments allow the mobilecommunicators to be informed e.g. whether a spouse or a business partnerwill be late for a meeting because of traffic delays.

In yet another embodiment, the TSP can modify the size of the user-zonebased on the traffic event. For example, even if a driver selected onlya 5 miles user-zone, but if the accident caused a 7 miles traffic jam,the TSP may override the user selection and reset the extent of theuser-zone to 7 or even 8 miles. This allows the driver to becomeinformed about the traffic jam before actually reaching it.

FIGS. 5A-E illustrate certain features of the above method 100.

FIG. 5A illustrates that the location of the driver (the diamond label)is determined in step 122 a, e.g. from cell-tower data or GPSinformation. A user-zone is selected in step 123 a, either definedduring the initialization or recalled from stored data. As the drivermoves, her location and the user zone are updated in regular intervals.The TSP received traffic information about various locations in thearea. By practicing steps 111-113 the TSP identified two trafficaccidents in the area, 125 a and 125 ax. These traffic events wereidentified through steps 111-113 by employees of the TSP integratingchopper data and cell tower data. However, the driver is not burdenedand her radio program is not interrupted by information about theseidentified traffic events, as neither of these identified traffic eventsis selected, as they are both outside the driver's user-zone.

FIG. 5B illustrates the changed situation, when the most recent updateof the driver's location 122 b and her user zone 123 b makes theidentified traffic event 125 b to fall within the updated user zone 123b. In an embodiment of step 120, the TSP selects the identified trafficevent 125 b based on the updated user-zone of the mobile communicator.With little or no delay the TSP carries out step 130 and alerts thisspecific driver to the traffic event 125 b ahead of her. The alert ispassive and does not require the driver to launch an application on hermobile communication device. In the same alert the TSP does not informthe driver about the identified traffic event 125 bx, as that does notfall within the user's updated user-zone 123 b.

FIG. 5C illustrates that in relation to the identified traffic event 125c either the TSP or the driver changed the shape and extent of theuser-zone in step 123 c. Motivations to enlarge the user-zone includeexploring the status of alternate routes. Since enlarging the user-zonemade the identified traffic event 125 cx also fall into the user-zone,the TSP also selects identified traffic event 125 cx. Then, in a step130, the TSP alerts the driver to selected traffic event 125 c and 125cx. The alert may indicate that not only the main highway 101 has atraffic accident, but the first choice alternate route 126 cx also hasan accident 125 cx. This alert may allow the driver to choose secondaryalternate route 126 cy, where accidents do not slow down traffic.

FIG. 5D illustrates another embodiment, where in the step 123 d theuser-zone is selected based not on the location of the driver but basedon the location of the traffic event 125 d.

FIG. 5E illustrates an embodiment where the user-zone is selected instep 123 e based on the location of a selected house, such as thedriver's home, or the school of the driver's children.

FIG. 5F illustrates an embodiment, where the TSP defines not only auser-zone 123 f, but also an event-zone 127 f. In these embodiments, theidentified traffic event is selected for a particular mobilecommunicator, when the user-zone 123 g of the mobile communicatoroverlaps with the event-zone 127 g of the identified traffic event, asshown in FIG. 5G.

FIG. 5H illustrates that the user zone 123 h can have a hierarchicalstructure, including hierarchical layers 123 h-1, 123 h-2, and 123 h-3.In embodiments described below, different type of services can beprovided to the mobile communicator as the identified traffic event 125h falls within different hierarchical layers 123 i.

FIG. 5I illustrates that in some embodiments the event-zone may have ahierarchical structure, including hierarchical zones 127 i-1, 127 i-2,and 127 i-3. In these embodiments, the mobile communicator may beoffered different services as the user-zone 123 i overlaps withdifferent hierarchical zones 127 i as will be described below.

FIG. 5J illustrates that in some embodiments the extent and shape of theuser zone can be varied in time, depending on changing trafficconditions. For example, the user-zone can be shrunk from 123 j-1 to 123j-2 when an overturned truck is removed and thus the TSP expects thatthe delays will be reduced.

FIG. 5K illustrates that in some embodiments the extent and shape of theevent zone can be varied in time, depending on changing trafficconditions. For example, the event-zone 127 k-1 can be extended to 127k-2, when the original accident is followed up by a chemical substancespill and thus the TSP expects that the delays will be increased.

FIG. 5L illustrates that in some embodiments the user and event zonescan be defined in terms of stations of a communication system. Aparticular embodiment defines the zones in terms of the towers of acell-phone network: T1, T2, . . . . In particular, the user zones 123l-1 and 123 l-2 can be determined in terms of the communication towerskeeping track the identification numbers (ID's) of the mobilecommunicators, such as cell phone users. In FIG. 5L the mobilecommunicator communicates with tower T4, thus the user-zone 123 l-1 ofthe mobile communicator 122 l-1 gets defined as an area corresponding totower T4, and the user zone 123 l-2 of the mobile communicator 122 l-2gets defined as an area corresponding to the tower this mobilecommunicator is communicating with: T3.

The traffic event, or incident, 125 l happened between towers T1 and T2.The event-zone 127 l is defined as an area corresponding to towers T1and T2. Visibly, in the illustrated situation the user-zone 123 l-1 ofmobile communicator 122 l-1 does not overlap with the event-zone 127 l,and thus mobile communicator 122 l-1 does not get alerted in step 130.In contrast, the user-zone 123 l-2 of mobile communicator 122 l-2 doesoverlap with the event zone 127 l and therefore mobile communicator 122l-2 gets alerted in a step 130.

In some cases, the event-zone is elongated along the highway itself. Theevent zone 127 l can be asymmetric, i.e. longer for the direction ofmobile communicators approaching the traffic incident 125 l and shorterfor mobile communicators leaving the area of the traffic incident 125 l.

The direction of motion of mobile communicators can be determined fromacquiring tower data repeatedly. For example, at a time t the TSP, orany other agent, may acquire the data that on a north-south orientedroad, a mobile communicator contacted a tower Tn. Then, at a subsequenttime t′, the TSP/agent may record that the same mobile communicatorcontacted a second tower Tm, which is located south from tower Tn. Fromthese data the TSP/agent may infer that the mobile communicator ismoving southward along the road. As explained above, the TSP may usethis directional information to define the event zone 127 l.

FIG. 5M illustrates an embodiment when the event-zone 127 m-1 getsextended from 127 m-1 to 127 m-2. Visibly, the tower-defined user-zone123 m-1 does not overlap with event-zone 127 m-1 and thus mobilecommunicator 122 m-1 does not get alerted when the event-zone is theoriginal smaller size 127 m-1. In this case only mobile communicator 122m-2 gets alerted.

However, it the TSP, or any other agent, re-evaluates the severity ofthe traffic incident, or the traffic jam builds up, then the TSP maydecide to increase the tower-defined event zone from 127 m-1 to 127 m-2.In this case the mobile communicator 122 m-1 also gets alerted in analerting step 130.

FIG. 5N illustrates another embodiment of enlarging the event-zone 127n-1 to 127 n-2. Mobile communicator 122 n has a tower-defined user-zone123 n, defined essentially as an area belonging to tower T3. A trafficevent or incident 125 n was identified between towers T1 and T2. At theearly stages of the incident, there was only a limited buildup oftraffic jam, thus the event-zone was defined as 127 n-1, which impactedonly towers T1, T2 and T4. At this stage only mobile communicators,whose user-zones 123 n overlap with the event-zone 127 n-1, will receivealerts. In embodiments, where the user-zone is defined by towers, themobile communicators who are communicating through towers T1, T2 and T4,will be alerted. Accordingly, mobile communicator 122 n is not alertedat this stage.

However, at a subsequent time the traffic service provider TSP mayintegrate updated traffic information, e.g. by carrying out steps111-113, and conclude that the size of the traffic jam expanded ontosubsidiary routes 126 nx and 126 ny. In order to alert mobilecommunicators on those roads, as well as helping approaching mobilecommunicators, who maybe contemplating taking these subsidiary routes,the service provider may decide to extend the event-zone into 127 n-2.As the FIG. 5N illustrates, the enlarged event-zone 127 n-2 may includetowers T3, T5 and T6. In tower-defined user-zones this means that themobile communicators who are communicating through these towers, will bealerted. According to FIG. 5N, user 122 n will be alerted after theenlargement of the event-zone to 127 n-2.

In various embodiments this enlargement procedure may take forms. E.g.the event zone may be constructed not as a single ellipse, but as acollection of elongated areas, formed along the main route and thesubsidiary routes. These elongated areas can be updated, modified andvaried independently from each other.

Also, the enlargement step can be repeated more than once, involvingmore and more towers. Further, as the traffic jam gets resolved, e.g.the overturned truck gets removed at 125 n, the event-zone maybe reducedas well. Again, this can be done as an overall reduction, or piece-wise.Also, different towers may send out different alerts, as motorists mayface different traffic conditions ahead on the main road and on thesubsidiary roads.

FIG. 5P illustrates another embodiment, where alert messages are sentout to mobile communicators according to an estimate of the time themobile communicators will spend in the area of the traffic event.

In detail, the location of a traffic event 125 p can be entered on a mapby an operator of the traffic service provider TSP or by an automatedsystem. Additional information can be entered as well, such as apredicted clean-up time of the traffic event 125 p. Subsequently, a pathresolution algorithm can be applied to estimate the time which will bespent by different mobile communicators 122 p in the area of a trafficevent 125 p. This path resolution algorithm can compute the time for amobile communicator 122 p remaining on the main highway, and the timesfor taking alternate routes 128 p-1 or 128 p-2. For each path a time canbe computed and the alert messages can be sent out according to thecomputed times.

In some embodiments the longest travel times can be computed, e.g. byassuming that the mobile communicator 122 p gets red lights all alongthe main and the alternate routes 128 p. The routes could be evaluatedfor the longest travel time, not longest distance as these two criteriamay not coincide.

In some cases the algorithm may use a single recursive graph traversalto determine the corresponding travel times.

Some embodiments then proceed and create zones according to theestimated travel times. In some implementations a short, a medium and along travel time zone can be created. The zones can be determined inrelation to the tower locations, starting with the towers closest to thetravel event and include more and more towers as the radius of the pathsearch is enlarged. In the next step the TSP can interrogate the celltowers in the identified zones and generate lists containing the mobilecommunicators who are in the different zones. These zones can be storedand reused as the mobile communicators enter or exit the differentzones.

FIG. 5P illustrates this process, as the graph traversal algorithmidentifies zones 127 p-1 to 127 p-3 around travel event 125 p accordingto whether the estimated travels time is “short”, “medium” or “long”. Awide variety of definitions can be used to define what constitutes ashort/medium/long travel time. Next, cell towers T1-T3 are identifiedwhich track cell phones in zones 127 p-1 to 127 p-3, respectively.Subsequently, the identified cell towers T1-T3 are interrogated for themobile communicators 122 p-1-122 p-3 tracked by them. In this example,mobile communicator 122 p-1 will be entered into a “short time” list,mobile communicator 122 p-2 will be entered into a “medium time” listand mobile communicator 122 p-3 will be entered into a “long time” list,because they are tracked by cell towers T1, T2, and T3, respectively. Asmobile communicators move e.g. on the highway, they can be moved from afarther list to a closer list. E.g. mobile communicator 122 p-3 can bemoved from the long time to the medium time list when she crosses fromzone 127 p-3 to 127 p-2, or analogously, from being tracked by tower T3to being tracked by tower T2. Of course, in various embodiments thenumber of zones and lists can vary widely.

In a next step, different messages can be generated for mobilecommunicators on the different lists—corresponding to the differentzones, as implementations of step 130. For example, advertisements canbe selected based on the position, speed and direction of the movementof the mobile communicators in the zones.

For example, for mobile communicators on the short time list, the TSPmay send out a short time list alert/notification, for mobilecommunicators on the medium time list, a medium time listalert/notification, and for mobile communicators on the long time list,a long time list alert/notification,

The cell towers can be polled in appropriate time intervals, such asperiodically. The path evaluating algorithm can be either rerun, or usethe previously determined path-evaluation. Mobile communicators can beadded or removed based on a wide range of criteria, such as whether theymoved past the accident, or taken alternate routes or stopped at a gasstation or restaurant or other place.

In step 122, the location of the mobile communicator can be determinedpassively, i.e. without running an application on the mobilecommunication device.

In step 120, the traffic event can be selected without requiring themobile communicator to specify or program a traffic route. This is incontrast to some systems, which pair drivers and traffic accidents basedon the drivers entering their daily commute (or any other route ofinterest) onto a web-based system.

In step 130 the alert message is sent out passively. Embodiments of thisstep include alerting the mobile communicator without requiring themobile communicator to respond by using hands, e.g. to terminate orinterrupt an active application. This embodiment may be appreciated incountries or states where operating mobile phones with hand duringdriving is prohibited. Also, some systems require the driver to launchan application either to indicate their location to the TSP, or torespond to or process the traffic information, such as displaying a map,which shows the blocked highways. This requires interrupting e.g.ongoing telephone conversations: a disadvantageous feature.

The mobile communication device can be any known mobile communicationdevice, including a mobile telephone, a mobile computer, anycommunication device capable of sending a wifi or wimax signal, anycombination of these devices, e.g. a computer equipped with any sort ofdevice making it capable of communicating over any wifi, wimax or otherwireless network. In general, any electronic device configured tooperate in conjunction with any kind of mobile communication networks iswithin the scope of the term “mobile communication device”.

In step 130 the alerting may take place on a separate telephone line, ifthe mobile phone is configured to operate two or more phone lines.

The alerting step 130 may include alerting the mobile communicator withan alert-message, which includes at least one of an audio component, atext component, an SMS, a video component, a radio broadcast component,a television broadcast component, a multimedia component, and amultimedia messaging service component.

An example for an alert message is an audio component, which includes aring-tone, an instruction to tune to a traffic radio and a videocomponent including a live traffic camera broadcast.

In some embodiments, in step 130 the alert-message component can beselected based on a location of the mobile communicator relative to theselected traffic event, followed by alerting the mobile communicatorwith the alert-message component. Examples include providing moredetailed information as the driver gets closer to the accident.Embodiments include providing first just a statement of the trafficaccident, then, upon the driver getting closer to the accident site: thetotal time delay, then on further approach: which alternate routes totake to avoid the traffic jam, or which frequency to tune the car-radiofor additional information.

In this sense, the user-zone can be viewed as having a hierarchicalstructure itself: more detailed information is delivered to the mobilecommunicator when the identified traffic event moves from an outer layerof the user-zone to an inner layer of the user-zone. As mentionedbefore, in some embodiments the extent and shape of the user-zone may beupdated by the TSP, e.g. motivated by the increasing extent of thetraffic jam. In these embodiments, if the user-zone is enlarged by theTSP, the identified traffic event can move into an inner-layer of theuser-zone from an outer layer even if the mobile communicator is sittingin a traffic jam.

Alternatively, the TSP may define an increasing event-zone around thetraffic event. In these embodiments

These examples were specific realizations of “traffic utilityinformation” regarding the selected traffic event. Other embodiments ofthe traffic utility information include information regarding analternative route related to the traffic event, an expected duration ofthe traffic event, predicted times of arrival to points of interest,such as to a concert or to an airport, a parking information, an eventinformation, and a suitable exit near the mobile communicator'slocation.

The parking information can include the location of a parking garage andwhether that garage has empty slots or is it full. Combined exit andparking information can be especially useful near airports, concerts, orsporting events, where different auxiliary parking lots can beapproached through different exits, and the parking lots can fill up,inconveniencing drivers.

In some embodiments, the traffic information is updated in a regularmanner, e.g. when a prediction of a traffic delay is changed, or anoverturned truck has been moved to the side. This provides the mobilecommunicator with valuable information for making decisions.

The traffic utility information can be offered in response to the mobilecommunicator requesting more information, or can be offered byautomatically launching an application on the mobile communicationdevice.

The traffic utility information can be offered as part of anadvertisement-based non-paying service, or as part of a paying service.The paying service may include a monthly fee based service, a per-useservice, and a service, billed in relation to the bill of the mobilecommunication service.

Providing a traffic alert and traffic utility information in relation tothe location of a driver is a specific example of “location basedservices”, sometimes referred to as LBS.

Embodiments of the present alerting method can be viewed as “pushing”information to the drivers: a distinction from some existing methods,where the drivers have to “pull” information from a service provider. Assuch, the present method offers commercial opportunities to interestedsponsors.

FIG. 6 illustrates that the alert message in step 130 may containsponsored information from interested sponsors. Within step 130, in step131 information-sponsors can be selected based on the location of themobile communicator, and in step 132, sponsored information can beoffered to the mobile communicator, sponsored by the selected sponsors.Notably, the sponsored information may include advertisements.

For example, when the TSP determined that the mobile communicator, whoselocation was tracked in step 122, is facing substantial traffic delaysin the vicinity of exit 42, the TSP may carry out a search in aninternal database of ad-sponsors in a vicinity of exit 42, and thenoffer advertisements and promotions by these sponsors on the cell phoneof the mobile communicator, as described in more detail below.

FIG. 7 illustrates that sponsored information can be offered in ahierarchical manner within step 132. Embodiments include: (step 133)alerting the mobile communicator regarding the selected traffic event,(step 134) offering traffic utility information, and (135) offeringsponsored information, such as an advertisement.

The hierarchical information may be offered in hierarchical formats, orhierarchical components. These hierarchical components may include: anaudio component, a text component, an SMS, a video component, a radiobroadcast component, a television broadcast component, a multimediacomponent, and a multimedia messaging service component.

The hierarchical information may be offered in conjunction with thehierarchical structure of the user-zone or the event-zone embodiments ofFIGS. 5H-I. In some embodiments, a simple ring-tone is sent when themobile communicator enters the outermost hierarchical event-layer 127i-1. Subsequently, when the mobile communicator enters the nexthierarchical event-layer 127 i-2, a text message is sent to the mobilecommunicator's cell phone. Finally, when the mobile communicator entershierarchical event-layer 127 i-3, an application is launchedautomatically on the cell phone to rely more in-depth trafficinformation.

The video/television/media information in general, and theadvertisements in particular, may be offered in streaming format, indownload-and-play format, and in any other kind of audio-visual format.

Embodiments include the TSP generating a passive audio alert message forthe driver by generating a modified ring tone on the driver's cell phonewith an announcement that an accident lies ahead, and advising to takenear-located exit 100. Alternatively, the modified ring tone may onlyalert the driver to the selected traffic event ahead, and a text messagesent to the phone of the driver may display the expected delay or otherrelevant traffic information.

Once the driver takes exit 100 and opens the cell phone for furtherinformation, an application may launch automatically, or the driver maybe invited to launch the application (step 133). Once the application islaunched, it may present additional traffic utility information, such asa live video feed from a traffic helicopter, showing the accident site,or a web-based map, highlighting the delayed routes, including theactual estimated delay times for the main route and the primaryalternative routes, and possibly identifying non-delayed alternativeroutes (step 134). This can be followed by step 135, where sponsoredinformation is offered as e.g. web-based advertisements, or directsingle-cast of an advertisement to the cell phone of the driver. The adscan also be placed on the screen simultaneously with the traffic utilityinformation.

Examples of sponsored information include the ads of the restaurant,located near exit 100. Or the announcement of ongoing sales at theneighboring department store. Or a promotion (such as a price reduction)announced by a nearby gas station. The knowledge of the time delay willassist the driver to decide which promotional offer to accept at thenearest exit 100. The driver may prefer utilizing the service to avoidsitting in traffic for an inordinate amount of time, and instead usingthe time of the traffic jam for some overdue shopping.

In some embodiments, once the mobile communicator launches anapplication on his or her cell phone, the TSP may make part of thisapplication to relay individual location information back to the TSP. Inthese embodiments, the TSP receives one more type of trafficinformation: the individual speed of the mobile communicator, beyond theaverage speed information, available from the cell-towers. Thisindividual information can then be one of the collected trafficinformation used in step 111.

Some embodiments of the passive traffic alerting method 100 can besupported by the sponsors of the advertisements. As such, someembodiments can be offered without charge, in contrast to many present,fee-based services.

Mixed embodiments are also possible. In some cases the basic passivetraffic alert may be offered free of charge, but additional componentsof the hierarchical messages may be fee based. For example, the moredetailed traffic utility information may be provided for a fee, when thedriver launches an application on his cell phone. Or, if the driveraccepts an invitation for a promotional event, such as a sale in anearby department store, then the traffic utility information may beoffered free of charge.

Many forms of invitations can be implemented within the method 100. Forexample, a sponsor may offer a coupon to the driver in an electronicformat. A particular implementation is that the coupon contains a barcoded portion attached to the invitation. Thus, the driver can takeadvantage of the invitation by driving to the offering department store,purchase the offered item, and during check-out swipe her cell phonewith the stored bar code on its display over the laser scanner of thecheckout counter.

Many other promotional items can be offered electronically, e.g. thetickets of a nearby sports game or of an entertainment event. In someembodiments, the ticket itself, possibly with a bar code or with anyother identifying mark, can be sent electronically to the cell phone ofthe driver. Any one of these electronic promotional items, such asbarcodes, can offer free products or services, or partial credit towarda full price.

In some other embodiments the promotional items may offer delayedaccess, e.g. the sponsoring department store may offer a coupon, whichis valid for a multi-day period. Or, if a department store learns thatat a future time there will be a traffic jam nearby, e.g. because of aconstruction of an overpass, then the department store may transmit tothe driver coupons and barcodes which are valid at the future time ofthe traffic jam.

Some embodiments include “location-awareness” components. For example,on a highway leading from California to Nevada, a traffic accidentoccurs. The TSP determines the location of the mobile communicator e.g.from the data provided by the cell-phone service provider. If it isdetermined that the mobile communicator crossed the state-line and is inNevada already, then not only promotional messages of local stores canbe forwarded to her cell phone, but also gaming offers, e.g. bets whichcan be placed through the cell phone.

Some embodiments include various control mechanisms regarding thering-tone overriding function. To avoid enabling or even allowing thecreation of undesirable ring-tone overrides, various oversight functionscan be implemented.

FIG. 8 illustrates an embodiment of messaging the mobile communicator.The TSP can alert the mobile communicator with a passive alert messageregarding the selected traffic event in step 137.

Then, in an open application, the TSP can provide basic broadcastinformation in response to the mobile communicator requesting moreinformation in step 138.

Finally, in a premium application, sponsored information can be providedto the mobile communicator in step 139. The sponsored information can beof any variety described within this application, including in-depthtraffic information, location based services, such as parkinginformation, sales-related information, event information, promotionaloffers.

In some embodiments mobile communicators can program their intereststhrough their cell phones, or through any other electronic communicationdevice, such as their computer, specifying the type of promotionaloffers they more interested in receiving, or whether they are interestedin getting alerted about other routes, such as their family membercommute routes.

In some embodiments the delayed mobile communicator may be invited tospecify third party alerts, e.g. the TSP may offer alerting a familymember or a co-worker of the delayed mobile communicator.

In some embodiments, the mobile communicator is enabled to interact withthe mobile communication device via voice commands. Embodiments includeordering the mobile phone to launch a traffic-related application, or tomodify the user-zone, or to notify a third party about the delay themobile communicator is experiencing.

In some embodiments the TSP responds to the mobile communicator'srequests by an Interactive Voice Response (IVR) system. For example, thering tone may alert a driver of a traffic event ahead. In response, thedriver may call a preprogrammed number, preferably by a single click onthe phone. From this number, the driver may be provided furtherinformation regarding the traffic event.

FIG. 9 illustrates a related traffic alerting method 200, including thesteps identifying traffic events from analyzing traffic information(step 210), selecting a user-zone based on a location related to amobile communicator (step 220), selecting an identified traffic eventbased on a relation of identified traffic events and the user-zone (step230), and alerting the mobile communicator with a passive messageregarding the selected event (step 240).

FIG. 10 illustrates a related traffic alerting method 300. Method 300includes identifying traffic events from analyzing traffic information(step 310), selecting an identified traffic event based on a locationrelated to a mobile communicator (step 320), and alerting the mobilecommunicator regarding the selected traffic event with a plurality ofmessages in a hierarchical order (step 330).

FIG. 11 illustrates embodiment 400 of a traffic alerting method. Inparticular, FIG. 11 shows the generating of the alert message in detail.In this embodiment, once the traffic event or incident occurs (410), instep 420 a determining of the alert zone gets carried out. An operator,agent, or traffic service provider, may first rate the incident data:how serious is the incident, how long delays can be expected. Theratings can be based on multiple factors, including video, helicopter,police, sensor, remote camera and other types of data. The rating of thetraffic incident can be identified by carrying out earlier-describedstep 110.

Then the operator or agent can overlay three types of maps: a locationof the incident, the map of cell phone towers, and the roadmap. From theoverlaying of these three maps the operator or agent can identify thealert zone, or event zone. In this embodiment the alert/event zone canbe identified in terms of mobile communication stations, such as cellphone towers. The towers which are within the alert zone will bereferred to as impacted cell phone towers. They include the towers inwhose vicinity the traffic incident occurred, plus the towers alongwhich a buildup of a traffic jam is either expected, or alreadyobserved. The extent of the alert/event zone can be updated repeatedly:it can be expanded or contracted as events on the ground evolve:expanded as the traffic jam builds up and contracted as the trafficobstacle gets removed.

In the same step 420 the service provider may determine the alert whichcorresponds to the incident. E.g. the nature of the trafficevent/incident can be determined. Examples include: the alert mayspecify the duration of the delay, or the type of the accident (e.g. howmany cars are involved, etc.)

In step 430, cell phone tower data can be acquired and processed. Forexample, the identification numbers, or IDs, of mobile communicators canbe collected from the impacted cell phone towers. This will identify forthe service provider all cell phone users within the alert zone. Thisacquisition may be referred to as tower ID dump.

In step 440, the subscribers can be filtered out from the ID'd cellphone users, whose ID was acquired from the impacted towers. This willenable the service provider with a list of users, or mobilecommunicators, who should be provided with service from the dumped IDs.

In step 450, matching of appropriate alert can be performed. In somecases this involves determining an appropriate alert. Embodiments canmaintain control over applications which generate the alert message.These embodiments can avoid the generation of inappropriate messages,which can be an important consideration. This control function issometimes referred to as a gateway function, or “gatewaying”.

In the same 450 step, other application data may be queued on theservers of the service provider. These data may include making furtherdata available, as well as video, audio and other type of information,regarding e.g. the traffic incident. This step readies other informationto provide full information application to the cell phone of the user.

In step 460 the composed appropriate message can be sent to the phone ofthe subscriber of the service. This message is typically a passive alertmessage.

FIG. 12 illustrates in more detail the path 460 of the alert messageonce it has been generated by the service provider.

In step 465 the alert message is generated, as described e.g. in steps410-450 above and in steps 510-550 below.

In step 470 the service provider provides a gateway service. Asindicated above, a purpose of this service is to prevent unauthorizedusers to generate inappropriate messages. In some embodiments thegateway service provides an authentication code associated with thealert message.

In step 475 the carrier, or aggregator also operates a gateway service.In some cases this carrier/aggregator gateway can search for theauthentication sign from the service provider's gateway, and keep ordiscard the alert message depending on whether proper authentication hasbeen identified.

In step 480 the mobile or cell phone of the individual subscriber oruser may receive the alert message from the carrier.

In step 485 the alert message is actually processed by a client orapplication running on board of the cell phone of the subscriber oruser.

FIG. 13 illustrates another embodiment 500 of the method. Embodiment 500shows in detail the generation of the content and format of the alertmessage.

In step 510, alert information is received by the system provider. Inresponse, the system or service provider may start composing an alertmessage. In this first step, the alert message could be composed by alive person. This step can be performed in parallel to step 420, wherethe incident is rated. The live person may integrate information fromvarious sources, including police reports, video feeds, cell tower dataabout the speed of passing motorists, sensors, cameras, etc. Then thelive person may construct the alert message. This may involve composinga live message, or may involve text-to-speech conversion.

In step 520 the alert message can be composed. The alert message caninvolve an audio component, graphics, and various alert methods by thephone, such as buzzing, lighting up, vibrating, blinking, displayingtext, or any other triggering. In some embodiments the phone may have a“talking telephone” application present, which makes the phone “talk” tothe subscriber.

In step 530 the alert may be compiled. This may involve alert formats,including Qualcomm-CMX, MPS, Audio, Q-CELP, AAC and any other codecs forcell phones. It can also involve Multi Media Services (MMS), which caninclude audio, video, and text components. In some cases proprietaryformats can be also utilized. This step maybe carried out in parallelwith step 450 above.

In step 540 the server formats the alert message for the phones. In someembodiments the acquired and filtered IDs carry the handset profiles.These handset profiles carry information concerning the format thehandset expects to receive its messages. Today about 2800 types ofhandsets are in use, and they require a wide variety of formats. Theseinclude the universal 3rd generation standard 3gpp, Apple's AAC, MP3,png, jpeg formats and many other types of restrictions, such as maximumnumber of characters etc.

To accommodate this expectation, the servers may establish a largesorting mechanism. This includes a sorting table, which lists all thesubscribers and their handset profiles. In step 530 the alert messagehas been compiled in all known formats. In sorting step 540 the servermay rout the message in a particular format to all those handsets, whoseprofile indicates that they expect the message in this particularformat. In simple terms, the server assigns the alert message in aspecific format to those handsets which expect the message in thatspecific format.

In some embodiments, the subscriber may also specify additionalpreferences, such as at a given time he prefers to receive the alertonly as a vibration but not as a voice alert. The handset profile maycarry this information as well. In response, the server may rout analert message to the subscriber, which is formatted accordingly, e.g.without the voice component.

This system is different from the system often used today, when thesorting system includes a large number of stacked dedicated servers,each specialized for formatting messages into a single format.

Step 550 illustrates the gateway function by the service provider, wherethe alert messages can be authenticated by a gateway.

Step 560 illustrates the gateway function by the carrier, which checksthe authentication by the service gateway.

When finally the alert message reaches the phone, it will be processedby the on-board application, as e.g. in step 485 in FIG. 12. Thesemirroring gateways 550-560 allow for a safe communication between theservice provider and the handset, and in particular the client on thehandset, of the individual subscriber.

Other embodiments of the above method include a broadcast-based MobileAlerting Network (MAN) Platform and service 1000, implemented in apush-to-talk-equivalent (PTTE) environment.

FIG. 14 illustrates the operation of the MAN service 1000.

Step 1100 may include identifying an Alert Area corresponding to anevent location.

Step 1200 may include identifying subscribers in the Alert Area.

Step 1300 may include broadcasting an Alert Message to the identifiedsubscribers in a push-to-talk-equivalent environment.

An example of MAN service 1000 can be practiced as follows.

In step 1100, a traffic event can be identified, e.g. by a “SkyPlatform”: “Accident occurred at exit 39 on highway 80”. There can bemany ways to identify the accident as described earlier in relation tosteps 110, 210 and 310. These include: from traffic camera information,from Cell Tower data, signaling slow car speed, from roadside sensors,or from traffic helicopters, as described earlier. The traffic event canbe identified by using a single information source, or by integratinginformation from more than one of the above sources, as describedearlier in this application.

The event can be any one of a wide variety of events, including atraffic accident, a weather alert, a recreational or sports event, or anE911 emergency situation, e.g. a chemical or hazardous material spill,possibly threatening with a health hazard.

The Sky Platform can then determine an Alert Area passively i.e. withoutrequiring communication with a central system of the Carrier Network.The Alert Area can be defined in terms of cell towers: the Sky Platformidentifies which cell towers belong to the Alert Area. In the aboveexample, the Alert Area includes the Cell Towers which manage the cellphone traffic in a suitably defined vicinity of exit 39 on highway 80.The Alert Area is an embodiment of the event zone 127, describedearlier.

In step 1200, a group of subscribers of the Broadcasting Alert systemcan be identified in relation to the Alert Area, e.g. by a Sky TrackerModule. The Sky Tracker Module can acquire the list of users who arepresently registered with or are in communication with the Cell Towersin the Alert Area. Then the Sky Tracker Module can cross reference thisuser list with a list of subscribers of the MAN service. The subscribersmay be identified e.g. by overlaying the event zones 127 a-p of theAlert Area with the above described user-zones 123 a-p, preset by thesubscribers.

Other methods include identifying subscribers by operating a SensorArray, as described below in relation to Sensor Array-based MobileBroadcasting Alert (SAMBA) service 2000 below.

The subscribers can be identified by their subscriber mobile ID, or bytheir International Mobile Equipment Identity (IMEI), or by any otherhandset identification information, such as an IMSI or MIN number, or bytheir phone number.

In cases of extreme emergency, such as a radioactive or chemical spill,a rapidly advancing fire, or a mudslide, all users will be selected, notjust subscribers.

In step 1300, an Alert Message 1301 can be prepared and broadcast to theidentified subscribers by a master broadcaster. The master broadcastercan be a Broadcast Module of a server of the MAN service 1000.

In prior systems, such as user-to-user push-to-talk systems, thecommunication was only point-to-point type. Master broadcasters were notused in push-to-talk environments.

In contrast, the MAN service 1000 may broadcast the Alert Message 1301in a Push-To-Talk (PTT) network or Integrated Digital Enhanced Network(IDEN). PTT and IDEN are mobile telecommunications technologies, whichprovide their users the benefits of a trunked radio and a cellulartelephone. Since in these systems the traffic is unidirectional (whenthe user signals the desire to talk by pushing a button, the traffic inthe incoming direction is stopped), the required frequency widths of thechannels are narrower. Thus, these PTT and IDEN systems are capable ofmanaging more users in a given spectral space, compared to analogcellular and two-way radio systems. Some of the techniques used by PTTand IDEN systems use speech compression and time division multipleaccess (TDMA). The MAN service 1000 may also be integrated into a GSMsystem.

The Alert Message 1301 can include a Short Message System (SMS) message.

FIGS. 15A-B illustrate a network architecture of the MAN service 1000,using SMS messages.

FIG. 15A illustrates that in existing carrier networks the shortmessaging system (SMS) allows users to send short messages to other cellphones. These messages are typically sent to the full (typically tendigits) phone numbers of the targeted single users. In commercialapplications, short codes can be utilized as target “phone numbers”.

In an example a TV or radio broadcast invites listeners to send apurchase order in the form of a predefined SMS message addressed to ashort code of only five digits, where the short code is linked to a fullregular phone number. E.g. a disc jockey can prompt her listeners topurchase and download a ring tone composed by a band called “Band” ontotheir phone by announcing: “Text ‘Band’ to 12345 to get your newring-tone composed by the Band”. Texting “Band” to 12345 by a user mayprompt a commercial transaction: the downloading of the band's ring-toneto the user's phone, possibly associated with a payment for thedownload. Other examples include a purchase of a band-relatedmemorabilia or a placing a vote in a contest. The payment for thiscommercial transaction is sometimes linked to the phone bill of theuser, or to a previously set up account.

Managing these commercial transactions is a considerable task. Theactual commercial transaction is carried out by prompting a vendor todeliver the purchased item e.g. through a download or through regularchannels such as by mail. In turn, the user's account is reached andbilled. The manager of these transactions communicates with the Carrierto get authorization for the transactions and to pay for the servicesprovided, among others. If the user has an account with one Carrier butthe transaction is taking place through another Carrier, then aCarrier-to-Carrier communication also takes place.

To manage these complex tasks, presently cell phone Carrier Networks1001 typically utilize SMS Aggregators, or SMS Controllers 1010. TheseSMS Aggregators, or SMS Controllers 1010 manage the SMS-basedtransactions in large volumes, in bulk. E.g. an SMS Aggregator 1010 mayenter into a contract with a Carrier 1001 for managing a million SMSmessages per month. These SMS Aggregators/Controllers 1010 can be set upphysically at or near the high level national or regional centers of theCarrier Networks.

The network topology can have different forms. In same cases the SMSAggregators 1010 have direct connection to the Users-1 . . . n, inothers the primary connection is between the Users-1 . . . n and theCarrier Networks 1001.

An even smaller number of service providers, sometimes a single nationallevel entity, may manage the assignment of the short codes. Theassignment of a particular short code to a particular full phone numbercan be purchased for specific periods, e.g. the run of a promotioncampaign, or a TV program. Or, it can be purchased for a long period, onan ongoing basis.

FIG. 15A illustrates certain existing SMS-based systems. Users-1 . . . ncan be in communication with the SMS Aggregator/Controller 1010, e.g.sending a text message to a short code, requesting a commercialtransaction. The SMS Aggregator/Controller 1010 can be in communicationwith a Vendor 1002 and facilitate the commercial transaction, such asthe mailing of a T-shirt of a band to a User. The SMSAggregator/Controller 1010 can also communicate with Carrier 1001-1, onwhose network (towers, servers, switches, etc) the actual transaction istaking place, e.g. on a “fee per message” basis. The fee can be a fixedsum or a “revenue-split” percentage of the transaction. If some of theusers, such as User 1 and User 2 have their phone account with adifferent Carrier 1001-2, then the SMS Aggregator 1010 may locate theaccounts of User 1 and User 2 at Carrier 1001-2 and bill these accountsin relation to the transaction on Carrier 1001-1.

The SMS Aggregators 1010 often use the TCP/IP, such as theshort-message-peer-to-peer-protocol (SMPP) to place their messages inbulk. The commercial aspects, such as the actual payments, can becarried out in the framework of premium SMS, or PSMS systems.

FIG. 15B illustrates embodiments of the present MAN Service 1000. TheMAN Service 1000 can be provided instead of, or in parallel to theregular SMS Aggregators 1010. In some cases, there can be acommunication link between the MAN Service 1000 and the SMS Aggregator1010. The MAN Service and Platform 1000 can be connected between Users-1. . . n and Carrier 1001-1 and Carrier 1001-2. The MAN Service andPlatform 1000 can also directly communicate with the Vendors 1002-1 . .. n.

In some embodiments, the MAN Service 1000 can communicate bybroadcasting promotional offers to the Users-1 . . . n in relation tothe Alert Messages 1301, in a Push-To-Talk-equivalent environment, asdescribed next.

FIGS. 16A-B illustrate embodiments of some of the Alert Messages 1301which can be sent by the MAN Service 1000. These Alert Messages 1301 canhave more than one part. In some cases the Alert Message 1301 cancontain three parts.

FIGS. 16A-B illustrate a general case of a three part Alert Message1301. Part 1310 a can alert the subscribers and inform them about thecause of alert, such as an event or an accident. FIG. 16B shows anexample 1310 b: the Alert Message “accident at exit 39” is displayed onthe phone's display as an SMS message.

Part 1320 a can offer Alert Message related choices in general. Anexample is 1320 b: the phone displays the SMS: “Press key 2 for audioreport”, or “Press 2 to receive the Alert Message in audio format”. In arapidly increasing number of countries, manual operation of mobile phonehandsets is prohibited while driving. In such countries opting toreceive the message in audio format may be preferred by manyuser/subscribers. If the user/subscriber pressed “2” to receive theAlert Message 1301 in audio format, then portions of the Alert Message,such as the cause of the alert and subsequent event-related informationcan be delivered in audio format.

The Alert Message 1301 can be implemented in a “Push-To-Talk”environment. In such implementations the lead part 1310 of the AlertMessage 1301 can already be an audio message. Implementations on CarrierNetworks, which provide real Push-to-Talk services can include sendingto and playing on the handset a direct audio announcement, without anyaction required from the subscriber, announcing that an accidenthappened at exit 39. This is an implementation of step 130 above, wherethe mobile communicator is alerted with a passive message, which doesnot require the launching of an application or client. In fact, it doesnot require any initial manual operation from the subscriber—anadvantage in traffic-related applications, for example.

In “Push-To-Talk-Equivalent” (PTTE) implementations, the incoming SMSmessage may wake up the Alert Client, which has been downloaded onto thehandset previously, to announce that “An accident happened ahead. Formore information, press 2”. In the rest of the application the PTT andPTTE implementations will be generally referred to as PTTEimplementations.

Part 1330 a may offer event related choices. Part 1330 b is an example:the phone displays the SMS offering a “hot key” which translates to aphone number: “Press key 5 for more information or for a phoneconnection to a vendor at exit 39”. Or, the phone speaker may state thesame, if key 2 was pressed in 1320 b. By pressing the hot key 5, theindividual subscriber/user can retrieve further information. In someembodiments, pressing such a “hot key” can activate a client, which iscapable of connecting to an internet web address of a vendor describinga promotion through an Internet protocol. In other embodiments, pressingthe hot key can connect the user to a vendor who placed the promotionalAlert Message.

An example of 1330 b is an SMS message being displayed: “At exit 38, allpizzas are 20% off at Domino's. For more information, press 5”. Pressing5 can activate a client on the handset, which proceeds to download aMulti Media message, such as an internet based web page, an audio, avideo or a message in any other media format, which provides informationabout the offer at Domino's.

Several different types of multimedia messages can be downloaded on thephone, including coupons and bar-codes related to promotions, and moreannouncements. Such coupons or barcodes can be stored on board. When thesubscriber walks up to the counter at Domino's to pay for his pizza, thesubscriber may pull up the stored bar code on the screen of the cellphone and hand the phone over to the check-out clerk. The clerk mayswipe the display over a sensor, which recognizes the bar code and givethe customer the 20% discount.

Another example of 1330 b is displaying offering an option: “To beconnected to Domino's by phone, press 5”.

FIG. 17 illustrates the modules and their interaction of a MAN system1400, associated with the above MAN service 1000.

An Alert Information Service 1410 can provide the informationsubscribers are interested in and subscribed for.

FIG. 18 illustrates a specific example of a MAN system 1400, where theAlert Information Service 1410 includes a Sky Platform 1412, asdescribed above, which identifies traffic events of interest, such astraffic jams or hazard conditions, as described in relation to steps110, 210, 310, and 1100 in previous embodiments. The Sky Platform 1412may then determine the Event Location and a corresponding Alert Area inrelation to the identified Event Location.

In the above traffic example, the Identified Event may be a traffic jamat exit 39. In this case the Sky Platform 1412 may identify the sectionof highway 80 between exits 35 and 39 as the Alert Area.

Returning to FIG. 17, the Alert Information Service 1410 may be coupledto a Subscriber Selector 1420. The Alert Information Service 1410 canprovide information to the Subscriber Selector 1420, which identifiessubscribers who should be contacted related to this information.

FIG. 18 illustrates that the Sky Platform 1412 can be coupled to aSubscriber Selector such as a Sky Tracker Module 1422 and can forwardthe Identified Event and Alert Area to it. The Sky Tracker Module 1422can then select subscribers who may be interested in the informationrelated to the Identified Event. This determination can involvecross-referencing the list of users registered at Cell Towers in theAlert Area with a list of subscribers.

In embodiments using e.g. Cell Tower data, no GPS application needs tobe activated on the handset to locate the subscribers. These embodimentshave higher operational speed and require less battery power from thehandset than GPS based applications. Nevertheless, the Subscriberselector can also utilize GPS to locate subscribers in otherembodiments. Yet other embodiments can use the Sensor Array-based MobileBroadcasting Alert (SAMBA) systems 2400, as described below in relationto FIG. 25.

In the above traffic example, the Sky Tracker Module 1422 may identifythe Cell Towers which serve the drivers in the Alert Area on highway 80between exits 35 and 39, request and receive the list of all cell phoneusers who are registered at these Cell Towers, and cross reference thislist of registered users with a subscriber list to establish whichsubscribers to reach.

The Alert Information Service 1410 can be a wide variety of otherservice providers, who provide information related to traffic, sports,finance, news, emergency, or entertainment. In many of these cases, theinformation service is not necessarily location based. In someimplementations, the information is event based, such as the end of aball game, or the closing of the stock market, or tickets becomingavailable for a show, or hotels rooms becoming available at a reducedrate, or the end of a bidding, betting, or voting period. In thesecases, the Subscriber Selector 1420 may select all, or a large fractionof the subscribers who are within the service area.

The Subscriber Selector 1420 may contact a Broadcast Module 1430 withthe Alert Information and the list of Selected Subscribers. In someembodiments, there is a direct communication link between the AlertInformation Service 1410 and the Broadcast Module 1430. In some of thesearrangements the Alert Message can be assembled without knowledge orreference to the Subscribers.

In the Example of FIG. 18, the Broadcast Module 1432 can receivecommunication form either the Sky Platform 1412 or the Sky Tracker 1422,or both.

In any one of these arrangements, the Broadcast Module 1430 may generateand assemble an Alert Message in response to the communication from theAlert Information Service 1410 and the Subscriber Selector 1420.

The Alert Message can contain the message portion 1310 a-b related tothe Identified Event and may offer the event-related promotional choices1320 a-b.

These promotional choices may originate at Promotional Agents 1440.

As FIG. 18 illustrates, such Promotional Agents 1440 may include AlertArea Vendors 1442 in the Alert Area, or in its proximity.

In the above traffic example, the Alert Area Vendors 1442 can includethose fast food vendors, who are contracted with the provider of the MANservice 1000 and are located in the proximity of exits 35 to 39, such asthe Domino's pizza at exit 37. For example, the headquarters of theDomino's fast food chain may have set up a running contract with theprovider of the MAN service 1000, which lists the location of allDomino's restaurants where the MAN service 1000 is available. Thecontract may specify that every time a traffic event occurs, the MANsystem 1400 shall identify the Domino's which is located within theAlert Area, e.g. the stretch between exits 35-39, as Alert Area Vendor1442. This step is analogous to step 131, where information sponsorswere identified based on the area of the handset user. Then theBroadcast Module 1432 can generate an Alert Message related to thetraffic jam at exit 39, which includes an offer of discounted pizza atthe Domino's located at exit 37.

As shown in FIGS. 17 and 18, the Alert Message is then broadcast by theBroadcast Module 1430/1432 to Alert Clients 1460-1, 1460-2, . . . 1460-nwhich have been downloaded onto the subscriber's Handsets 1470-1, 2, . .. n. The Alert Message is typically broadcast through one or moreCarrier Networks 1450.

As discussed above, running an application on a handset can drain thepower from the handset fast. Therefore, it is advantageous that theAlert Clients 1460 can be a small client on the handset. Thus, while theAlert Client 1460 is active on the handset, it may require only minimalpower to operate and poses only a limited demand on the battery of thehandset. In some PTTE implementations, the handsets may have only aminimal Alert Client 1460. And, as explained earlier, for the initialstep of receiving the Alert Message, some PTTE implementations may notuse an Alert Client 1460 whatsoever.

The Alert Message can be structured as follows. While the length of theSMS messages in principle could vary in a wide range, presently thelength of the typical SMS message is 160 characters. Thus,implementations of the above three part Alert Message 1310-1330 can be160 characters long.

The actual SMS of the Alert Message may contain the followingcomponents:

<date, time, message ID, size, hot key#>

The date and time can provide a time stamp for the message. The “messageID” can identify a prestored message already on the phone. In a simpleexample “message ID=1” can wake up a client on the cell phone which thengenerates the audio message: “To get more information about the event,press 5” (the number of the hot key). In more complex installations, adatabase can be stored on the handset, containing entries for allvendors who are associated with the MAN service 1000. In the abovetraffic example, “message ID=223” can identify Domino's as one of thesevendors, generating the display or audio message: “To be connected toDomino's by phone, press 5”.

In some implementations, the MAN service 1000 may not be based solely onlocation or traffic. E.g. the MAN service 1000 can be based on events.An example is a service associated with a sports club, such as theYankees. This implementation of the MAN service 1000 may send an AlertMessage to a subscriber when the Yankees game is over. A “messageID=272” may launch a pre-recorded audio announcement on the phone: “TheYankees game is over. To receive the result of the ball game, press 5”.

The MAN service 1000 can be associated with a wide variety of events.The events can be weather related, e.g. alerting subscribers totornados. Or, the service can be financial, alerting the subscribers ifa stock goes below a price level: “The stock GOOG dropped below $500. Toget a stock update, press 5”.

FIG. 19 illustrates that managing the Alert Messages in relation to theSMS queue and the various subscriptions in parallel may be a complextask. Some implementations carry out these functions with deploying aWrapper 1500, possibly as a part of the Alert Client 1460.

The functions of the Wrapper 1500 may include:

1510—Managing Alert Messages;

1520—Managing a mailbox function, including prioritizing messages;

1530—Downloading and updating applications;

1540—Managing subscriptions;

1550—Storing Data, related to messages and promotions; and

1560—Personalizing.

In detail, the Alert Message Manager 1510 may be capable of (i)recognizing an incoming Alert Message within the SMS queue, (ii) pullingit from the queue without disrupting the active SMS sessions, and (iii)presenting the Alert Message to the subscriber.

It is often the case that the subscriber has several SMS sessions activeon the handset. Some of these SMS queues can contain literally hundredsof SMS messages lined up. It typically requires manual operation (i) tomove from one SMS session to another, and (ii) to scroll to the mostrecent SMS message.

If the Alert Message were treated as one of the regular SMS messages, itwould not serve one of its central functions, alerting. The WrapperAlert Message Manager 1510 is an application, which can review allincoming SMS traffic, and is capable of identifying the Alert Messagesas non-regular SMS messages and process them accordingly. The WrapperAlert Message Manager 1510 can pull the Alert Messages from the SMSqueue and display them with the highest priority. In someimplementations, the wrapper can perform these functions withoutbreaking the queue of the regular SMS messages, e.g. withoutdeactivating the active SMS sessions. The Wrapper Alert Message Manager1510 is capable of performing these functions without manual operationrequired from the subscriber.

If a subscriber subscribes to more than one Information or AlertInformation Service 1410, then the Wrapper 1500 may manage the variousAlert Messages through a Mailbox Module 1520. The Mailbox Module 1520can store alerts from different MAN services 1000.

In an example, a subscriber of several MAN services may be driving home.Her Traffic MAN service may broadcast a Traffic Alert Message regardingan accident ahead. The Wrapper Alert Message Manager 1510 may identifythe Traffic Alert Message, lift it from the SMS queue, attach thehighest priority “1” to it, and present it in a Push-To-Talk format tothe subscriber. The subscriber may choose to respond to the TrafficAlert Message by asking for more information regarding the accident.

During this transaction, her Financial MAN service may send a FinancialAlert Message regarding the closing prices of her stocks. The WrapperAlert Message Manager 1510 may again identify the Financial AlertMessage, lift it from the SMS queue, but attach to it a priority “3”,e.g. based on the initial setup of the Mailbox Manager 1520 by thesubscriber. Therefore, while the subscriber is processing the TrafficAlert Message, the wrapper may store the Financial Alert Message in aFinancial mailbox 1520-2. The Wrapper Mailbox Manager 1520 may presentthe content of the Financial Mailbox 1520-2 after the traffic-relatedtransaction has ended.

In another example, the subscriber can be making an actual phone callwhen a new Alert Message is received. The Wrapper Mailbox Manager 1520may then store the Alert Message in the corresponding Mailbox andpresent it after the phone call is finished. Or, if some Alert Messagesare given higher priority than phone calls, the Wrapper Mailbox Manager1520 may even interrupt the phone call and present the Alert Message.This may occur e.g. if the subscriber is making a long personal call,and the phone receives an emergency type E911 Alert Message about aradioactive spill on the road ahead.

The Wrapper Applications Manager 1530 may be able to review theapplications on board, communicate with the central servers of the MANservice and report the versions of the applications, and if newerversions are available, then reach out and locate the newer version,download them onto the phone, unpack the download and update theapplications by installing the newer version.

In an example, if the subscriber has a game on board, the WrapperApplications Manager 1530 may be notified by the game's provider that anewer version is available. Then the Wrapper 1500 may proceed anddownload the newer version of the game and install it on board.

The Wrapper Subscription Manager 1540 may be able to manage thedifferent subscriptions associated with the applications on board andthe Alert Messages. E.g. some of the applications may have a fixedtime-period license, or the updates may require payments. Some of theAlert Message Information Service providers 1410, such as the FinancialAlert Message Service, may also require fees, e.g. on a periodicalbasis. The Wrapper Subscription Manager 1540 can manage theseobligations.

The Wrapper Data Storage Manager 1550 may manage all storage functionsrequired by the various applications. E.g. some Alert Message ServiceProviders may wish to enhance the impact of their Alert Message, orsubsequent promotion message by sound effects. The service can beaccelerated if these sound effects are already stored on board. In somecases the Data Storage Manager 1550 may organize the over-writing ofstored data, if that data is out of date.

In an example, an Entertainment Alert Service provider may play a themesong, which was stored on board before presenting the actual message ofsurplus theatre tickets being available. Or, a Financial Alert Serviceprovider may start its message by a stock phrase announced by DonaldTrump, pre-recorded and stored on board.

While in some embodiments the Alert Message maybe transmitted within anSMS protocol, in other embodiments the Simple Mail Transfer Protocol(SMTP) can be used. This can be of importance as in some countries andin some situations it is increasingly difficult or even illegal, tocharge a fee for SMS transmissions. Further, in some areas in the UnitedStates, the SMS response time of the big carriers may slow downsubstantially e.g. in peak traffic hours, or after a sports game, insome cases to tens of seconds. Finally, the SMTP is compatible with therecently introduced 3GPP protocol, supporting extremely fast responsetimes. The above considerations underline that systems using the SMTPprotocol can be quite effective in supporting high speed communications,arid thus can be used to implement the Alert Messaging system.

In implementations which use SMTP protocols instead of SMS protocols,the Wrapper 1500 may be able to pull and activate the Alert Messagewhich arrived in an email format, and process it with highest priority.This is a departure from established mail protocol, which typicallyrequires the email recipient to actively pull up or acknowledge thereceipt of the email.

FIG. 20 illustrates the updating function of the Wrapper 1500. Thecolumns 1602-1608 represent four applications, which are required toproperly display a multimedia message (MMM), in response to thesubscriber requesting more information regarding the promotion. In anexample, the subscriber may wish to see a trailer or preview of a showin a MMM format, for which discount tickets are being offered.Displaying this MMM message may require the most recent version of avideo player, such as version 7 of the Flash or Shockwave video players.Other applications may include the Communication Protocol (CP), the RealTime Text Protocol (RTTP), or the QCP for the ring tones. In typicalsituations these sub-applications operate over the Operating System(OS), which itself may need updating.

The dotted line indicates the case when properly displaying a requestedMMM requires that the handset has version 7 of all the applications,players, plug-ins and protocols. Of course, in many cases, the latestversions have different version numbers.

The Wrapper 1500 may profile the handset and determine which versions ofthe applications are installed on board. In the present example, version3 of the application 1602, version 7 of application 1604, version 6 ofapplication 1606 and version 4 of application 1608 is on board.

After this profiling step, Wrapper 1500 may reach out to the MAN serviceprovider or the regular Carrier Network, locate version 7 of theapplications in need of updating, i.e. 1602, 1604, and 1608, anddownload and install version 7 of the identified applications on thehandset.

Some cell phones may not have the proper hardware for the MAN service1000. Thus, even downloading the required software may not prepare thephone for processing the MMM properly.

In fact, many phones simply do not have a speakerphone. In these phonesimplementing either the PTT-based MAN service 1000, or even the PTTEquivalent (PTTE) service can be a challenge. Some implementations cansolve this problem by the Wrapper 1500 profiling the hardware of thehandset as well, e.g. concluding that no speakerphone is available, thenlocate an application on the internet which can modify the ring-tonegeneration of the handset. Downloading and installing the ring-tonemodifying application may create a functionality with which the phone iscapable of alerting its subscriber to the receipt of an Alert Messagethrough the modified ring-tone, even if no proper speakerphone hardwareis on board.

Some implementations of the Alert Client 1460 and the Wrapper 1500 maybe as short as 32 kbyte. The power consumption of e.g. the Alert Client1460 can be further reduced in some implementations. The phone may beequipped with a motion or acceleration sensor. The subscriber may spendmost of the day in an office and thus may have little or no interest intraffic conditions. In such setups of the service, the power consumptionmay be reduced by switching off the Alert Client 1460 completely as longas the motion or acceleration sensor does not sense a (sufficientlystrong) motion or acceleration.

When the subscriber starts to go home, the motion or acceleration sensormay sense a sufficiently fast movement or acceleration. In response, itmay wake up the Alert Client 1460 so that it can start receiving trafficrelated messages. In other embodiments, the waking up of the AlertClient 1460 may be programmed according to the time of the day, e.g.waking up the Alert Client at 4:30 pm, if the subscriber typicallyleaves the office at 5 pm. Then the Alert Client 1460 may receive themessage about a traffic jam blocking the main route homes in time so asto advise the subscriber to choose an alternate route instead.

As illustrated in FIG. 18, the interaction of the Broadcast Module 1430and the Alert Clients 1460 can be of the “push-pull” type. The BroadcastModule 1430 sending the Alert Message is an initial push step. The AlertClient 1460 can then respond by pulling more information from theBroadcast Module 1430.

Implementations of the “pull” step can be prompted by the subscriber inresponse to Alert Message portion 1330 a-b. In the traffic example, thesubscriber is invited to press 5 to get a promotion. In the example ofFIG. 6, this corresponds to the step 132 of “offering sponsoredinformation”. In either case, the subscriber may choose to press 5,which prompts the Alert Client 1460 to pull additional sponsoredinformation to the handset from the Broadcast Module 1430.

The additional sponsored information can be of a wide variety. It can bea multimedia message, a webpage uploading on the handset via IP/WAP, amore detailed representation of the offer, an image of a coupon whichcan be redeemed, or a barcode.

Some embodiments of the system may be practiced in relation to personaldigital assistants (PDAs) or other integrated mobile devices, e.g.devices which have navigational/GPS capabilities.

Once the promotional multimedia message is retrieved or downloaded onthe handset, the Alert Client 1460 may play it without furtherintervention by the subscriber.

The downloaded additional information can be simply more information,such as providing a map to the location of the Promotional Agent 1440.However, in many implementations, the additional download can involve acommercial transaction. These implementations include urban MAN services1000, e.g. in large metropolitan areas alerting subscribers if a show ina nearby theater has unsold tickets available at reduced prices. In suchimplementations, the subscriber may want to initiate a commercialtransaction in response, such as buy the offered tickets.

Commercial transactions may require authorization and billingprocedures. The billing procedures can be managed through Billing Module1480, which can be in communication with Broadcast Module 1430 andPromotional Agent 1440, as shown in FIGS. 17-18.

In some existing systems, a manager of mobile commercial transactionsneeds to get an authorization from the Carrier Network which providesthe actual network services, from another Carrier Network which managesthe account of the subscriber who initiated the purchase, from theVendor, who is offering the product for sale, and the involved SMSAggregator. Getting the authorization of the purchase from all theseparties may pose considerable challenges.

In some implementation of the MAN service 1000 the authorization may bemuch simpler. (i) Since in the implementation of FIG. 15 the MAN serviceprovider can offer its service in parallel to the SMS Aggregator, theauthorization of the SMS Aggregator may not be needed. (ii) Second, thesubscriber may set up an account with the MAN service provider itself,and thus there may be no need to reach out to the Carrier Networksupervising the account of the subscriber to get another authorization.(iii) As mentioned above, from a regulatory point of view it isincreasingly difficult to charge users for SMS messages. Implementationsof the MAN service can overcome this regulatory problem by using theSMTP protocol instead of the SMS protocol, for which no such regulationsexist at present. All in all, implementations of the present MAN service1000 may not be burdened with Mobile Origination fees and time consumingbilling authorizations, accelerating the performance of the service.

Agents of promotional campaigns often desire to track the addressee'sresponse to the campaign. However, tracking systems face multiplechallenges. Carrier Networks do not provide “guarantee of service”, i.e.the delivery of SMS messages. Instead, today's standard is referred toas “best effort”, i.e. the Carrier Network makes a reasonable effort todeliver the SMS, but not more. The challenges include the following. (i)If the driver's handset started to receive an SMS message, but then thecar drives into a tunnel while receiving the SMS, the Carrier Networkmay not even know that the SMS was never properly delivered. (ii) SomeCarrier Networks will retry sending an SMS if an initial attempt todeliver it failed. However, the eventually successful delivery may takeplace only hours later. Since many of the promotional offers are timesensitive, such delays reduce the value of the promotional service. E.g.letting a subscriber know at 9 pm that there were reduced price ticketsavailable for an 8 pm show is of little value. (iii) The PromotionalAgents also may desire to know that even if the SMS arrived properly,did the subscriber actually request, or pull, the more detailedinformation. An Agent can be keenly interested to know what percent oftargeted users actually pull the more detailed information, such as thephotos of the new, deep-dish Domino's pizza, offered at reduced rates.(iv) The Promotional Agents also may desire to know that of thosesubscribers, who pulled more extensive MMM promotional information,which did place an order, such as actually buy the tickets for a showafter having viewed a trailer.

Implementations include a logger application 1600, which can carry outone or more of the above reporting functions. The logger application1600 may be deployed dominantly or exclusively on the handsets. Otherembodiments of the logger 1600 may cooperate more extensively withsupervisory applications sitting on the servers of the MAN serviceprovider. In most embodiments, the MAN servers can summarize the reportscoming in from the large number of logger applications, reporting theoperations of the individual handsets. These MAN servers can perform alarge variety of post-processing, collating, tabulating and analyzingthe reports. Eventually, the MAN servers can communicate these metrics,i.e. the summary and analysis of the reports to the Promotional Agents1440, such as the Alert Area Vendors 1442. These metrics can also beused in setting prices, revenue-splitting percentages in futurecontracts, and the share of Carriers etc.

FIG. 21 illustrates that step 1610 of the Logger 1600 may record andreport that the transmission of the Alert Message has been completed.

Step 1620 may include the Logger 1600 recording and reporting the timewhen the transmission of the Alert Message was completed.

Step 1630 may include the Logger 1600 recording and reporting that, inresponse to the Alert Message offering additional promotional material,the subscriber actually requested, or pulled the available promotionalmaterial.

Step 1640 may include the Logger 1600 recording and reporting that thesubscriber placed an actual order in response to the promotionalmessage.

In various embodiments different billing steps may be associated withthe different reports of the Logger 1600. E.g. a Promotion Agent may bebilled an increasing fee depending on whether the report regarding steps1610-1640 was positive. In some implementations a base fee can be billedif only the Alert Message was transmitted, a higher fee if it wastransmitted on time, an even higher fee if the subscriber pulled theadditional information, and a premium fee, if the subscriber actuallyplaced an order.

The Logger 1600 application can contain monitoring components to carryout these steps on board the handset. The monitored events can then berecorded either on board of the handset, or reported back to the serversof the MAN service, which record them. The reporting can be done eitherimmediately or after some collecting and buffering. Differentembodiments have different portions of the Logger applications deployedon board and in a centralized manner.

FIG. 22 illustrates a specific Alert Client 1700 including variousmodules as an example of Alert Client 1460.

An Alert Client 1700 may include an Operating System 1710, underlyingmost of its specific operations.

There can be numerous specific applications 1720 deployed over theOperating System 1710. Such applications were discussed in relation toFIG. 20, and may include: a Communication Protocol (CP), a Real TimeText Protocol (RTTP), a QCP for the ring tones, various Video players,among others.

Various controls and interfaces can be on board as well. These controls1730 may include User Controls, e.g. mapping keys to request functions:such as promoting a key to a hot key linking it to a website to requestMMM related to the promotions. A Storage Module may be present e.g. tostore promotional materials, such as a downloaded barcode. Such storagemodules may have a rolling erase function. Finally, a User Interface mayfacilitate e.g. the display of the downloaded bar code for swiping foreredemption.

Mailbox Module 1740 and its various functions have been describedearlier. In various configurations the Mailbox Module 1740 can be partof the Wrapper 1500, as described earlier.

The Remote Sensing module 1750 offers numerous options. These includethe provider of the MAN service 1000 being able to sense remotely theapplications and modules on board and initiate their updating, ifnecessary. Such an updating may be performed on a module-by-modulebasis. The Remote Sensing Module 1750 may cooperate with the Wrapper1500. Both of these modules may profile the handset, report the resultof the profiling and take action, such as updating modules on board.Some of their functions can be different though. The Remote SensingModule 1750 can be activated and controlled primarily from outside, suchas under the control of the MAN service provider. For this reason, somesubscribers may be reluctant to authorize such an expressly remotecontrolled Sensing Module. In contrast, the Wrapper 1500 may be a moresovereign module. When the subscriber wishes to download an MMM, theWrapper 1500 may, on its own, review the level of updates, necessary fordisplaying the MMM, compare this level to the level available on board,and initiate the necessary module updates. These steps are performed bythe Wrapper 1500 on its own control, without centralized commands.

Some Alert Clients 1700 may have room for personalized modules 1760 aswell.

As described earlier, some or all of these modules 1710-1760 may beaccessible to or even integrated with the Wrapper 1500 and Logger 1600Modules. The Wrapper 1500 may perform the just described updating andmanaging functions on any of the modules. It can also impact or evenoverride the applications which manage the SMS queues, such as the RTTPmodule, as described above.

The Logger 1600 may report to central MAN servers on the actions of anyof the modules, e.g. in relation to a promotional message or commercialtransaction. In an example, the Logger 1600 may record and report theactions of the SMS manager whether the reception of an Alert Message wasproperly completed. Or, the Logger 1600 may record and report whetherthe user engaged the User Interface to pull/request the additionalpromotional material. Or, the Logger may record and report whether theuser actually purchased a promotional barcode and stored it in thePromotion Storage module.

Some of the above implementations described the handset side of theoverall implementations.

Implementations of the MAN service 1000 also include web-basedinterfaces or platforms for the Promotional Agents 1440. Such aninterface may offer a wide variety of choices for a Promotional Agent1440, such as an Alert Area Vendor 1442.

FIG. 23 illustrates such a web-based Campaign Interface 1800. AParticipating Vendor may use such a Campaign Interface 1800 to publishvarious campaign items.

In module 1810 the Participating Vendor may specify the Type of AlertMessages he/she wishes to associate his/her promotions. In an example,an indoor skydiving venture along highway 80 may want to broadcastpromotional offers in case of a traffic jam occurring between exits 35and 40. Or a sports-equipment manufacturer may want to broadcast apromotional offer whenever the ballgame comes to a close at the nearbyballpark.

Since different Alert Information come from different Alert InformationServices 1410, the MAN service 1000 can act as a middle-man tofacilitate a contract between the Participating Vendor and the AlertInformation Services 1410.

In module 1820 the details of the Promotional Offer may be specified,such as the percent reduction in price of sports memorabilia after alost game, or a barcode or coupon to be downloaded for a show in anearby theatre, etc.

In module 1830 the Participating Vendor may specify the location aspectsof the Promotional Offer, such as the location of the store to go to,the location of the theatre of the show, etc.

In module 1840 the Participating Vendor may specify other logistics ofthe campaign, such as the duration of the Offer. Examples include untilthe traffic jam lasts, until the last ticket of the theatre show issold, etc.

In module 1850 the Billing Arrangements are worked out, possibly in aninteractive manner. The Participating Vendor may publish the desiredcampaign items 1810-1840 on the Campaign Interface 1800. In response,the MAN service provider may relay to the Participating Vendor that e.g.the Traffic Alert Information Service Sky Platform 1412 is willing toprovide the requested traffic alert information for a 30% split on allassociated revenues in the requested stretch of exits 35-40, or for afixed fee per Alert Message. Or that the local sports channel is onlywilling to provide Sports Alert Information Services for a ParticipatingSports Bar owner at a premium because the stadium did not fill up yet,etc. The MAN service provider also may report what cut the CarrierNetwork is asking. In response, the Participating Vendor may change someof the campaign items, such as the duration of the campaign, in order topublish a final campaign within its target budget.

The Reporting Module 1860 can provide feedback to the Vendor how thecampaign is going. The Reporting Module 1860 can have graphics andstatistical displays about the number of users who were reached by theAlert Message, the number of people who requested additional promotionalmaterial, and the number of people who actually realized a commercialtransaction. This information is primarily assembled by the MAN servicecenter from the reports of the individual Loggers 1600.

All of the above functions can be facilitated and managed by the MANSystem Manager 1900, deployed on MAN servers.

FIG. 24 illustrates that the MAN System Manager 1900 may include thefollowing Managers:

Alert Information Manager 1910,

Subscriber Manager 1920,

Broadcast Manager 1930,

Promotion Agent Manager 1940,

Carrier Manager 1950,

SMS Aggregator Manager 1955,

Alert Client Manager 1960, and

Billing Manager 1980.

These MAN Managers 1910-1980 of the MAN System Manager 1900 can bedeployed in Central Servers 1990 of the MAN System 1400. In some casesthere is a single MAN Central Server 1990, in others a hierarchical orflat network of MAN Central Servers 1990-1 . . . n.

One of the functions of the MAN System Manager 1900 is to facilitate,oversee and manage the operations of the corresponding modules of theMAN System 1400, as described in FIGS. 14-23. As such, the functions andthe operation of the MAN Managers 1910-1980 can be well understood fromthe description of the operation of the earlier-described correspondingMAN System Modules 1410-1480, in relation to FIGS. 14-23. Therefore, theabove functions and operations of the modules will not be repeated here.Instead, an example will be given to illustrate the cooperation of thecentral MAN Managers 1910-1980 with the MAN System Modules 1410-1480,Clients, Applications and Interfaces of the MAN system.

For example, Alert Client Manager 1960 can be configured to communicatewith the Alert Clients 1460-1 . . . n on board of the handsets 1470-1 .. . n. Also, the Alert Client Manager 1960 can work together with theindividual Wrappers 1500-1 . . . n on board of the handsets 1470-1 . . .n to carry out their functions. These functions were described inrelation to FIGS. 19-22 and include Managing Alert Messages, ManagingMailboxes, Managing On-board Application, Managing Subscriptions,Managing Storage and Personalization.

For example, the Wrapper 1500 on handset 1470-42 may profile its hosthandset 1470-42, and recognize that the RTTP has on old version onboard. Then Wrapper 1500-42 may communicate with the Alert ClientManager 1960 to request a new version of RTTP. The Alert Client Manager1960 may reach out and acquire the latest version of the RTTP,communicate with Wrapper 1500-42 and these two modules may cooperate todownload the new version of the RTTP on the handset 1470-42.

The Alert Client Manager 1960 may also cooperate with the individualLoggers 1600-1 . . . n on board. This cooperation can include receivingand recording the reports from the Loggers 1600-1 . . . n from thehandsets, including the successful completion of the reception of theAlert Messages, the subsequent pulling of promotional messages, and thecompletion of actual commercial transactions. The Alert Client Manager1960 may collect these reports from the individual Loggers 1600-1 . . .n, collect, archive, process, organize, and analyze them. The result ofsuch an analysis can be conveyed e.g. to the Promotional Agents 1440,e.g. through the Campaign Interfaces 1800.

These were only examples, to illustrate the possible cooperation betweenthe MAN Managers 1910-1980 with the individual MAN System Modules1410-1480. In a particular embodiment, various elements may not beinstalled, or may be connected differently.

Finally, a Sensor Array-based Mobile Broadcast Alert (SAMBA) service2000 and corresponding SAMBA system 2400 will be described.

FIG. 25 illustrates that the SAMBA system 2400 has many components whichare analogous to those of the MAN System 1400 of FIG. 17. The SAMBASystem Modules 2410-2480, which are analogously numbered as the MANSystem Modules 1410-1480 of FIG. 17, have analogous functions and willnot be described again. Blocks and modules, which were described inFIGS. 14-24 as analogous to those in FIG. 17 are also within the scopeof the equivalently numbered SAMBA System Modules 2410-2480.

FIG. 26 illustrates that a SAMBA System Manager 2900 may include thefollowing SAMBA Managers 2910-2980, deployed in a SAMBA Central Server2990:

Alert Information Manager 2910,

Subscriber Manager 2920,

Broadcast Manager 2930,

Promotion Manager 2940,

Carrier Manager 2950,

SMS Aggregator Manager 2955,

Alert Client Manager 2960, and

Billing Manager 2980.

The functions of the SAMBA Managers 2910-2980 are analogous to those ofthe MAN Managers 1910-1980, described in relation to FIGS. 14-24 andwill not be repeated here.

Some of the differences from the MAN system 1400 include that the SAMBASystem 2400 may locate and select subscribers differently thanSubscriber Selector module 1420 of the MAN system 1400. The location ofthe subscribers may not be determined by collecting Cell Tower data, asin some of the other implementations of the MAN System 1400.

FIG. 27 illustrates that, instead of the subscriber selector 1420, theSAMBA System 2400 may acquire location information using a specializedSensor Array 2420. The Sensor Array 2420 may contain a large number ofsensors 2421-1 . . . n, whose functionalities include receivingbroadcasts from cell phones and processing the received information.Such sensor arrays 2420 can be e.g. an array of the sensors manufacturedby Air-Patrol Corp. The two rays on the individual sensors indicate thespatial angles or reception. These sensors, or antennae, can beconfigured to be able to receive signals from the full spatial angle, orfrom a limited spatial angle. They can be installed in areas of greaterinterest, which have a higher density of subscribers. Areas ofinstallments may include: major traffic intersections, commuting routesleading in and out from metropolitan centers which are known to developtraffic jams and other problems, high density entertainment areas, suchas Disneyland, the Strip in Las Vegas, the highway section at the Nevadastate border line, where gaming becomes legal for drivers, the mainfloor of gaming operations, the theatre district in New York, thevicinity of sports venues, all kinds of educational settings such ascollege campuses, and airports, among others. Of course, implementationscan include any other areas of interest, e.g. corporate environments,high security environments, and federal environments.

FIG. 28 illustrates a Sensor Array Operation 2500.

In step 2510 one or more sensors 2421 can receive a signal of asubscriber mobile phone 2470. The scope of the term “signal” is usedvery broadly here. It can involve signals of any sorts. Embodimentsinclude signals associated with the phone managing an active phone call,or a data session, or processing SMS traffic. Or the signal can be aninduced signal, in response to a ping or tic-tac from an outside source.The signal may even be generated when the phone is in a passive state.

In step 2520 several of the 2421 sensors can cooperate to determine thephysical location of the broadcasting phone from the received signal.There are numerous ways to determine the location of the phone based onphone signals, including triangulation, GPS based methods, and moresophisticated techniques. Triangulation can be carried out by applyingwell known formulae based on wave propagation theory and geometricalrelations, applied to the signals received by three sensors. The spatialresolution of a Sensor or Antenna Array manufactured by the Air PatrolCorp. can be of the order of one or few feet.

The embodiments are described here in terms of cell phones. However, thescope of the embodiments is meant to be very general, as explainedearlier. The mobile communication device, or handset 1470 or 2470, canbe any known mobile communication device, including a mobile telephone,a mobile computer, any communication device capable of sending a wifi orwimax signal, or any combination of these devices, e.g. a computerequipped with any sort of device making it capable of communicating overany wifi, wimax or other wireless network. It can be any deviceconfigured to emit a self-identifying signal. In general, any electronicdevice configured to operate in conjunction with any kind of mobilecommunication networks is within the scope of the term “handset”, “cellphone”, or “mobile communication device”.

In step 2530 the identity of the cell phone and the corresponding useris established. This step may require cooperation between the SensorArray 2420 and the SAMBA Central Servers 2990 and will be described indetail in relation to FIG. 29.

In step 2540 the established location and the identity of the cell phoneis forwarded to the SAMBA Central Servers 2990. This location andidentity information can be used by the SAMBA Central Servers 2990 in amanner analogous to the MAN Central Servers 1990.

FIG. 29 illustrates a SAMBA Operation Display 2600. The circlesrepresent the locations of individual mobile phones or any other mobilecommunication devices within a space of operation of the SAMBA System2400, such as an entertainment venue, a convention center, or a trafficrelated space, such as an area of a downtown or a busy trafficintersection. Cell phones broadcast their identification information inregular intervals to signal their locations to nearby Cell Towers and toregister with these Cell Towers to receive service. In some cases theregular intervals can be in the range of a few seconds to 90 seconds.The sensors 2421 use these cell phone signals to determine the locationof the broadcasting cell phone e.g. by triangulation.

In these broadcasts the cell phones relay some of their identificationinformation, so that the Carrier Networks can locate them when anincoming call is trying to reach the phone. This identificationinformation may include the mobile ID, the International MobileEquipment Identity (IMEI), or any other handset identificationinformation, such as an IMSI or MIN. In some cases this identificationinformation can be a GPS information, which can then be used toestablish the MIN (Mobile Identification Number of the phone number ofthe handset. In some cases the identification information can be anycombination of the above.

In principle the triangulation or GPS information can determine theprecise location of the cell phone and the broadcast identificationinformation can determine the identity of the cell phone and its user.This information should be sufficient for the operation of the rest ofthe SAMBA system 2400, such as sending out Alert Messages and promotionsto the SAMBA subscribers among the localized and identified users.

For example, in a gaming application, a Sensor Array 2420 can beimplemented in a gaming establishment, such as a casino. Patrons may beapproached to subscribe e.g. when entering a gaming venue. Oncesubscribed, the subscribers can be sent an Alert Message that ablackjack table at a specified location became hot or more active, or abetting limit has been raised at blackjack tables in another area of thegaming floor.

In an educational application, a Sensor Array 2420 can be set up on acollege campus. The Sensor Array 2420 can track students on campus.Students can subscribe to different services, such as sports eventrelated services, education related services etc. Alert messages can besent to students who signed up for sport-related services, if there ise.g. a traffic jam around the football stadium. Or an alert message canbe sent to students who enrolled in a class in case the class iscancelled, or the field trip starts in a different location. Anemergency alert message can be sent to all students if a criminal orviolent activity took place on campus, advising the students of unsafeareas, or relaying police instructions.

In yet other implementations, a Sensor Array 2420 may track cell phoneswithout ever decrypting their identification information, onlydetermining their location. Such implementations may be used to trackmovement of cell phones only. In traffic implementations embodiments maybe used to determine only the speed of movement of the phones in aneffort to identify traffic jams. In entertainment implementations suchembodiments may be used to determine crowd movement patterns, e.g. tomap out under-visited areas on a casino floor. In these implementationsthe identity of the users is never determined, they remain anonymous.

The identification of the users may pose challenges as well. The SAMBAsystem 2400 may be deployed in settings where the density of thesubscribers is high. If two cell phone users walk near each other, closeto the resolution limit of the Sensor Array 2420, and the Sensor Array2420 receives broadcast from both of them, the Sensor Array 2420 maydetermine the location of two cell phones nearby each other anddetermine the identity of two cell phones broadcasting from this area,but may incorrectly assign the identities to the two cell phones.

FIG. 29 illustrates a SAMBA Operation Display 2600 of the Sensor Array2420 displaying the above problem. The SAMBA Operation Display 2600shows the described situation, when two cell phones 2470-1 and 2470-2are very close to each other physically. The Sensor Array 2420 mayreceive their broadcast and extract the two broadcast identificationnumbers, such as the IMEI, IMSI, MIN or other handset identificationinformation.

However, it remains a challenge to identify which IMEI, IMSI, MIN orother handset identification information belongs to which phone. Thisproblem can be exacerbated by the various system delays, which mayintroduce as much as 4-5 seconds of delay into the processing of theIMEI, IMSI, MIN or other handset identification information, by whichtime the patrons and their handsets may have moved a considerabledistance from the location determined by the Sensor Array 2420. Toaddress these challenges, some implementations of the SAMBA system 2400include verification cycles to determine the proper identification.

FIG. 30 illustrates an embodiment of an Identification—VerificationCycle 2700.

In step 2710 new patrons can be given invitations to subscribe/enroll tothe SAMBA Service 2000, in exchange of receiving some enticements, suchas a certain amount of free service. This invitation may be offered at acontrolled location, such as the entrance of a gaming floor. Thesubscription/enrollment may require sending a text/SMS message to anaddress. Text/SMS messages include the IMEI, IMSI, MIN or other handsetidentification information of the sending phone.

In step 2720 the patron can enroll into the SAMBA Service 2000 bytexting a message. The Sensor Array 2420 can pick up this message andextract the IMEI, IMSI, MIN or other handset identification informationof the enrolling patron.

In step 2730, in response to the text message, the patron may beinformed about the details of the SAMBA Service 2000, which lists itsadvantages as well as informs the patron about the tracking/locatingaspect of the service. The patron maybe invited to opt in into the SAMBAService 2000, having been informed about these tracking features.

In step 2740, the patron may opt in into the SAMBA Service 2000, e.g. bytexting “yes” to the previous address.

In step 2750 an Alert Client 2460 may be downloaded onto the patron'shandset. There are numerous ways to download a client, e.g. by making akey hot. The patron pressing the hot key can initiate the downloadwithout elaborate actions by the patron.

In step 2760 the Alert Client 2460 may report to the SAMBA servers 2990the phone number or any other identification information of the patron.

In other embodiments of the Identification—Verification cycle 2700“tic-tac”-ing can be used as well, which can involve interrupting andrestarting the various communication channels to the handsets. When thecell phone attempts to restart various connections and reopen thecommunication channels, such as internet based connections, itrepeatedly broadcasts its IMEI, IMSI, MIN or other handsetidentification information and/or phone number. These broadcasts can beused to verify the identification information.

During these Identification and Verification Cycles 2700 the IMEI, IMSI,MIN or other handset identification information and phone number maybetransmitted more than once. The steps after the first receipt of thephone numbers serve as verification cycles. This aspect may serve as asafeguard that indeed that patron gets enrolled who opted into the SAMBAservice 2000 and not a person nearby who is not interested in benefitingfrom the SAMBA service 2000.

The phone numbers and IMEI, IMSI, MIN or other handset identificationinformation can be used to develop a database regarding the patrons.Cross-linking the location and identity of the patrons, and recordingtheir movement and commercial activities is of interest to PromotionAgents, and can be the basis of extending the above described MAN andSAMBA services to offer more specific offers to subscribers, where thePromotion Agents may expect a higher level of interest from thesubscriber. These analogous and equivalent services are all within thescope of the present application.

Returning to FIG. 29, in some embodiments of the SAMBA Operation Display2600, different classes or groups of users can be indicated by differentsymbols, such as symbols with different size, color or other identifier.Handsets 2470-10, -11, -12 illustrate examples of such differentsymbols. These symbols can correspond to a wide range of customeridentifiers. Possible identifiers include any kind of demographic dataor data about the purchasing habits of the user. In a gamingimplementation these identifiers may reflect the playing habits orplaying levels of the user, such as whether he/she is a high roller.

The SAMBA Central Server 2990 may use any kind of data bases toassociate these data with the identified users in the described graphicmanner. In other embodiments, actual letters, labels or texts can bedisplayed associated with the symbols. All of these implementations mayassist a Promotion Agent 1440 or 2440 to efficiently use the campaigninterface 1800 to push out advertisements to the appropriate users whichis of high interest for them. Such implementations increase thelikelihood of the targeted subscriber initiating a commercialtransaction based on the Alert Message or Offer.

In a gaming implementation, the identification-verification cycle 2700may identify subscribers of the SAMBA service 2000. Then the SAMBACentral Server 2990 may use a data base to identify high rollers amongthe subscribers. The SAMBA Operation Display 2600 may indicate regularplayers with a blue symbol and high rollers with a red symbol. APromotion Agent 2440 may then choose to broadcast different promotionoffers to regular players and to high rollers. E.g. the Promotion Agent2440 may broadcast only to high rollers that a new set of tables havebeen opened up only for high rollers in a VIP area of a gaming floor.

In an educational implementation students enrolled in different classesmay be indicated by different color symbols. In an example, a PromotionAgent 2440 may send out an offer regarding a software update only tostudents who are enrolled in computer science classes.

In a further aspect, various mobile services may need to utilizeconfidential information regarding the users of the mobile service.Examples include users of the Passive Alert System 100, the MAN system1000, or the SAMBA system 2000, which require knowledge of the locationof the service user with some precision. Since the location of a usercan be used by other parties not necessarily to the advantage of theuser, keeping the location of the user confidential can be a featureusers expect or require from such Mobile Alerting Services.

Other examples include mobile financial mobile services, where theowners of confidential information may be unwilling to releaseconfidential information without assurances that the records will betreated as confidential, or without verifying that the requesting partyhas authority to access these records. Examples include a financialinstitution not willing to release financial information, such as thestocks held by a user, to a mobile financial alerting service.

In response to such needs, some embodiments may incorporate aconfidentiality function. These systems can be referred to as neutralparty systems, third party systems, “Switzerland” systems, or MobileSubscriber Detection Authorization and Verification System (MSDAVS)systems 3000.

FIG. 31 illustrates such a MSDAVS system 3000. When a mobile serviceuser decides to opt-in to a mobile service, she/he can communicate thisintention to a MSDAVS 3100 directly or with the assistance of a MobileApplication Service Provider (MASP) 3200. The MSDAVS 3100 may include anOpt-in Database 3110, Service Policy Database 3120, and any other typeof databases 3130. The mobile service user can provide an explicitpermission for the MSDAVS 3100 to access confidential information from aConfidential Information Owner 3300 and can name a purpose for which theMSDAVS 3100 can use the accessed confidential information. Examples ofthe Confidential Information Owner 3300 can include a Wireless Carrier3310, who can release the location or any other confidential informationof a mobile phone user, or a Mobile Information Service Record Owner3320, or a Financial Record Owner 3330, or an Owner of Any OtherConfidential Information 3340.

The purpose of the release of the confidential information can includeopting-in to the mobile service provided by the MASP 3200. For example,the Wireless Carrier 3310 can release the location of a subscriber tothe MSDAVS 3100 for the specific purpose of participating in a locationbased service by a corresponding Mobile Traffic Network 3210, such asthe passive alert service 100, the MAN service 1000 or the SAMBA service2000.

Other types of Mobile Application Service Providers 3200 include OtherLocation Based Services 3220, Financial Services 3230, and any OtherMobile Information Services 3240.

Embodiments of the MSDAVS 3100 can enforce the permissions andauthorizations of the mobile service user, and protect the confidentialdata in such a way that both the confidential information owners and themobile service users are assured that no unauthorized access of theinformation will occur.

The MSDAVS 3100 can perform these confidentiality functions throughuser-friendly but secure means, such as through mobile communicationdevices, internet/web pages or other mechanisms. The MSDAVS 3100 canalso provide similarly easy-to-use de-activation, or de-authorizationmechanisms.

The MSDAVS 3100 can provide nearly real-time access to confidentialsubscriber information, as well as being scalable to a large number ofsubscribers of mobile services.

FIG. 32A illustrates an implementation and the operation of the MSDAVSsystem 3000. Some implementations can be based on a hosted service thatcan be accessed via web services by Mobile Application Service Providers3200. As mentioned above, the mobile service user can authorize theaccess of the confidential information directly through the MSDAVS 3100or with the assistance of the MASP 3200.

The MASP 3200 can offer a potential user a mobile service and indicatethat enrolling into the service is based on an opt-in procedure.

In step 32A-1, prompted by the offer, the potential user can send anopt-in authorization and possibly registration information to the MSDAVS3100 via a text message, a web command or an interactive voice response,or IVR technology that allows a computer to detect voice and keypadinputs.

In step 32A-2 the MSDAVS 3100 can store the authorization andregistration information, such as the telephone number and the name ofthe mobile service, in the Opt-in Database 3110.

In step 32A-3 the MSDAVS 3100 can communicate with its ServiceDescription Database 3120 about which MAPS 3200 to interact with andnotify about the opt-in and what type of authorization is required forthis service.

In step 32A-4 the Service Description Database 3120 can respond bynaming the appropriate MASP 3200 and the specifics of the mobileservice, such as authorization levels.

In some cases, information regarding the MASP 3200 may be attached tothe opt-in message, in which case steps 3 and 4 are not necessarilyperformed.

In step 32A-5 at least some of the opt-in and the registrationinformation of the potential user can be transmitted to the MASP 3200.

In step 32A-6, the MASP 3200 can respond by a mobile service relatedmessage. This message can include an identification of a ConfidentialInformation Owner 3300, and an identification of the confidentialinformation requested, such as the location of the opted-in client, or afinancial record of the opted-in client.

In step 32A-7 the MSDAVS 3100 can query the identified ConfidentialInformation Owner 3300 about the requested confidential information,together with the authorization of the user and a “neutral party”certificate, to assure the Confidential Information Owner 3300 that theuser's information will be handled confidentially and at the request ofthe user herself/himself.

In step 32A-8, the Confidential Information Owner 3300 may respond withthe requested confidential information, possibly attaching or repeatingthe terms of use, or the expected level of confidentiality.

In step 32A-9 the MSDAVS 3100 can respond to the user reporting that therequested mobile service is available and a confidential handling of thecorresponding confidential information has been set up by the MobileSubscriber Detection Authorization and Verification System 3100. Afterthese steps 32A 1-9 the user can start the regular use of the mobileservice.

The opting-out process can be performed through analogous steps, exceptthat it involves the removal of the registration information of the userfrom the Opt-in Database 3110.

In opt-in processes which are assisted by the MASP 3200, the MASP 3200may manage the details of the opt-in and opt-out process partially or inits entirety. In such implementations, the MASP 3200 can send the opt-inand opt-out messages to the MSDAVS 3100.

Different levels of integrity can be associated with different services.If the opt-in process was performed directly by the MSDAVS 3100 then ahigh level of integrity can be associated with the opt-in orregistration information. If the MASP 3200 performed the opt-in process,then a different, for example lower level of integrity can be associatedwith the opt-in or registration information. The level of integrity canbe communicated both to the user and to the Confidential InformationOwner 3300. The user can authorize the release of information ondifferent levels corresponding to the different levels of integrity ofthe Opt-in process.

FIG. 32B illustrates an embodiment where the MASP 3200 is handling theopt-in process.

In step 32B-1, the user can opt-in either indirectly though the MSDAVS3100 (step 32B-1), which opt-in message is then forwarded to the MASP3200, or through the MASP 3200 directly (step 32B-1′).

In step 32B-2 the MASP 3200 can register the opt-in and registrationinformation, such as the telephone number of the user, and notify theMSDAVS-3100 about the registration.

In step 32B-3 the MSDAVS 3100 can send a verify communication to theService Description Database 3120, which can respond by anacknowledge/not acknowledge (ACK/NAK) signal in step 32B-4.

In step 32B-5 the MSDAVS 3100 can store the registration information inits Opt-in Database 3110, which can now include not only the user'sregistration information but also the information regarding the MASP3200. As in other embodiments, the registration information can containvarious levels of authorization for accessing various levels ofconfidential information. The rest of the steps can proceed analogouslyto the embodiment of FIG. 32A.

Some embodiments of the MSDAVS 3100 can handle different types of mobileservices in connection to different types of Confidential InformationOwners 3300.

Next, specific embodiments of MSDAVS 3100 will be described.

Some embodiments include a Traffic-MSDAVS 3001, specialized for trafficrelated mobile alerting services. Examples include the traffic-orientedMobile Passive Alerting service 100 and a traffic-oriented MAN service1000. As described above in detail, some embodiments of these servicescan identify alert zones or Alert Areas in response to a trafficcongestion or traffic alert information and then provide mobile servicesfor the users in the Alert Areas.

FIG. 33 illustrates the operation of such a Traffic-MSDAVS System 3001,in relation to a Mobile Traffic Alerting Service 3211, after users optedinto the service. Examples of this Mobile Traffic Alerting Service 3211can include the Passive Alerting Service 100 and the Traffic-orientedMAN Service 1000.

In step 33-1, the Mobile Traffic Alerting Service 3211 can request fromthe MSDAVS 3101 the telephone numbers registered at the cell towers inan Alert Area. Here the Alert Area could be determined by a largevariety of ways, as described above, based on traffic congestion ortraffic alert information acquired from one or more sources.

In step 33-2, in response, the MSDAVS 3101 may inquire about therelevant service policies from its Service Description Database 3121.

In step 33-3, the Service Description Database 3121 may respond with theservice policies, levels of confidentialities, etc.

In the optional step 33-4, the MSDAVS 3101 may contact a Cell TowerDatabase 3301-1 for a list of the cell towers which are in the AlertArea. It may often occur that the Alert Area extends to the region ofmore than one cell towers, in which case all cell towers within theAlert Area can be listed.

In the optional step 33-5, the Cell Tower Database 3301-1 may providethe list of the cell towers in the Alert Area. These cell towers may beoperated by different wireless telephone operators.

In step 33-6, the MSDAVS 3101 may contact the Wireless Carriers 3311 whohave the listed cell towers in the Alert Area, querying them for all thephone numbers which are registered at the listed cell towers in theAlert Area. If optional steps 4 and 5 were performed then the list ofcell towers is provided by the Cell Towers Database 3301-1. If theseoptional steps were not performed, then the Wireless Carriers themselvescan be requested to identify the cell towers in the Alert Area.

In some embodiments, the Wireless Carriers 3311 themselves operate aGlobal Telephone Number Database 3301-2, or a Global Service ProfileIdentifier (SPID) Database 3301-2. This database may also include HomeLocation Register (HLR) and Visitor Location Register (VLR) Databases.In other embodiments, an entity separate from the Wireless Carriers 3311can be approached to provide the phone numbers. Such entities, somewhatanalogous to (SMS) Aggregators, may manage databases which mirror theTelephone Number/SPID Database 3301-2 of the Wireless Carriers 3311.This request may be accompanied by the presentation of some level ofauthentication of the neutral, or third party status of the MSDAVS 3101.

In step 33-7, the Telephone Number/SPID Database 3301-2 may provide thelist of all telephone numbers which are registered at the cell towers inthe Alert Area back to the MSDAVS 3101.

Typically, in wireless systems the cell phones do not register theirtrue phone numbers with the cell towers. A primary reason for this is toincrease the security and confidentiality of wireless systems. Instead,cell phones have their “true phone number”, such as their MobileIdentification Number (MIN) on GSM systems, or Electronic Serial Number(ESN) on CDMA systems, or Mobile Equipment Identification (MEID) in someplanned future systems, fixed on the phone (e.g. on the SIM card), butnot sent out after an initial registering or confirmation process.During regular operations, cell phones have a temporarily assignedvirtual, or logical, phone number, often called an International MobileSubscriber Identity (IMSI) and an International Mobile EquipmentIdentifier (IMEI), which indicate the virtual phone number, the makerand brand of the mobile phone, the network it is registered with andother information, respectively. These numbers can change in regularintervals, sometimes as often as a few times a day. Cell phones identifythemselves to cell towers by sending out these IMSI/IMEI numbers, thuspreserving a higher level of security.

There are large database operators, who manage “look-up tables”, i.e.the correspondence between the virtual IMSI/IMEI phone numbers and theMIN/ESN/MEID numbers, which are needed for the actual identification ofthe subscribers. These Databases can include the Home Location Registry(HLR) and Visitor Location Registry (VLR) for roaming users. Theselook-up tables can be managed by the Wireless Carriers 3311 directly, orby some additional entities, which mirror the database maintained by theWireless Carriers 3311. The actual identification of the subscribers andtheir phone numbers in steps 6-7 can include the use of these look-updatabases.

Steps 4-7 may result in dumping all phone numbers, registered at celltowers in the Alert Area, for the Mobile Traffic Alerting Service 3211.This step is performed in communication with the Wireless Carriers 3311and the Telephone Number Databases. Requesting the bulk, or completelist of telephone numbers registered at cell towers in the Alert Areatypically costs a small fraction of the cost of requesting the locationof each cell phone subscriber from the Wireless Carrier separately(“dipping”) and then determining whether the cell phone user is in theAlert Area. This latter approach would typically require alocation-identification by triangulation or a GPS or GPS-equivalentmethod with an unnecessarily high accuracy, such as determining thelongitude-latitude of the user by the Wireless Carrier 3311.

Instead, the Mobile Traffic Alerting Service 3211 can operate based onthe lower-accuracy location information of whether the cell phone iswithin the Alert Area. This location information can be generated bysimply dumping all cell phone numbers registered at cell towers in theAlert Area, without performing any individual triangulation.

Further, the high accuracy method may require regular/continuous updatesfrom the Wireless Carrier 3311, multiplying the cost. For all the abovereasons, the described dumping of all numbers registered at the AlertArea cell towers can be much cheaper and faster than the individualtriangulation approach. As such, it is an efficient gateway to higheraccuracy location information based services.

In step 33-8, the MSDAVS 3101 can forward the list of all phone numbersin the Alert Area to the Opt-in Database 3111. The Opt-in Database 3311can cross-reference or filter this list of all phone numbers against theregistered users of the Mobile Traffic Alerting Service 3211 and createa list of the subscribers of the Mobile Traffic Alerting Service 3211within the Alert Area and their phone numbers.

In step 33-9, the Opt-in Database 3311 can send this list back to theMSDAVS 3101.

In step 33-10, the MSDAVS 3101 can send the list of the subscribers ofthe Mobile Traffic Alerting Service 3211 within the Alert Area and theirphone numbers to the Mobile Traffic Alerting Service 3211. This enablesthe Mobile Traffic Alerting Service 3211 to start the traffic alertingservice to the subscribers in the Alert Area.

FIG. 34 illustrates the implementation of the above steps regarding theflow of the IMSI/IMEI and MIN/ESN numbers in a particular embodiment ofthe Traffic-MSDAVS 3001. When the cell towers are identified in theAlert Area by the Mobile Traffic Alerting Service 3211 and the MSDAVS3101, such as cell tower 2421, all the IMSI/IMEI numbers, sent by thecell phone hand sets 2470-1, . . . n to this cell tower 2421 areforwarded to the Traffic-MSDAVS 3101 either directly or indirectlythrough the Mobile Traffic Alerting Service 3211. The Traffic MSDAVS3101 can then acquire the complete list of MIN/ESN corresponding tothese IMSI/IMEI numbers from the Wireless Carrier 3311 or anotherTelephone Number Directory/SPID Database Manager, who mirrors the phonenumber look-up table of the Wireless Carrier.

The Traffic-MSDAVS 3101 can then cross-reference, or filter the completelist of the ESN/MIN numbers against the list of subscribers with thehelp of the Opt-in Database 3111 and inform the Mobile Traffic AlertingService 3211 about the IMSIE/IMEI numbers of the subscribers of theMobile Traffic Alerting Service in the Alert Area. With thisinformation, the Mobile Traffic Alerting Service 3211 can startproviding the Mobile Traffic Alert Service to the identified subscribersin the Alert Area, such as to handset 2470-2, indicated by boldoutlines.

In some embodiments the confidentiality of the confidential information,such as the true identity of the subscribers, encoded in their ESN/MINnumbers, and their location, can remain protected. In these embodiments,the Mobile Traffic Alert Service 3211 does not acquire the true identityof the subscribers: this information remains protected at the trustedTraffic-MSDAVS 3101. Further, the Mobile Traffic Alert Service 3211 doesnot store or track the location information of the subscribers either.These confidentiality measures ensure e.g. that the Mobile TrafficAlerting Service 3211 does not keep spamming the subscriber after thesubscriber exited the traffic Alert Area, or at a later time no agencycan access these confidential information, not even by compelling theMobile Traffic Alerting Service 3211.

FIG. 35 illustrates a Traffic-MSDAVS-MAN System 3002. Most blocks andtheir function are analogous to those of FIG. 17 and will not bedescribed here. A difference relative to the MAN system of FIG. 17 isthat the Subscriber Selector 1420 is replaced by the MSDAVS 3102. TheMSDAVS 3102 can provide the Broadcast Module 1430 with the list ofidentified subscribers e.g. according to the protocol described inrelation to FIGS. 31-34. In response, the Broadcast Module 1430 canprovide the Mobile Traffic Alerting Service to the identifiedsubscribers in the Alert Area.

FIG. 36 illustrates the Traffic-MSDAVS MAN System Manager 3212. FIG. 36in analogous to FIG. 24 and the similarly labeled elements will not bedescribed here. A difference relative to the MAN System Manager 1900 ofFIG. 24 is that the subscriber selector 1420 is replaced by theTraffic-MSDAVS 3102. The Traffic-MSDAVS 3102 can provide the SubscriberManager 1922 and the MAN Central Server 1992 with the list ofsubscribers in an Alert Area, identified e.g. according to the protocoldescribed in relation to FIGS. 31-34. In response, the MAN CentralServer 1992 can provide the Mobile Traffic Alerting Service to theidentified subscribers in the Alert Area.

FIG. 37 illustrates a Sensor-Based MSDAVS, or SAMBA-MSDAVS system 3003.In embodiments of the SAMBA-MSDAVS system 3003 the SAMBA Service 3223can acquire the IMEI/IMSI of all cell phones in an operation area, suchas a gaming floor of a casino, any office or workplace, conference,sports, high density traffic space, or educational space, includingexhibit centers, sport-stadia, busy intersections, hose-raceviewing/betting areas and college campuses. This can be achieved by thesensor array system of the SAMBA service 2000, as described in relationto FIGS. 25-30, especially FIGS. 27 and 29. This step can be analogousto acquiring the list of all cell phone numbers registered at celltowers in an Alert Area in the Traffic-related applications.

It may be preferred to introduce a well defined operational area for theSAMBA service 2000 and SAMB-MSDAVS System 3003, to enhance theconfidentiality of the service. Examples include having the sensor arrayoperate specifically on a gaming floor of a hotel, but not in the upperfloors, where the rooms are located.

In the SAMBA-MSDAVS System 3003 the Sensor Array 2420 can provide a listof all IMEI/IMSI sensed (virtual/logical) phone numbers to theSAMBA-MSDAVS Service 3223. Any kind of sensor arrays can be implementedbased e.g. on WiFi or cell phone sensors.

In step 37-1, the SAMBA-MSDAVS service 3223 can forward the completelist of sensed IMEI/IMSI phone numbers to the MSDAVS 3103.

In step 37-2 the MSDAVS 3103 can request the service policy regardingthis SAMBA-MSDAVS service from its Service Description Database 3123,which can respond in step 37-3 with the service policy regarding thisservice, such as levels of authorization required for accessing variousconfidential data, level of integrity of the service, and level oftracking and storing the data, if at all.

In step 37-4, the MSDAVS 3103 can forward all sensed IMEI/IMSI phonenumbers to a Telephone Number/SPID Database 3303. This Database 3303 canperform the look-up function and identify the ESN/MIN corresponding tothe sensed IMEI/IMSI numbers.

In step 37-5, the Telephone Number/SPID Database 3303 can return thecomplete list of MIN/ESNs, corresponding to all the sensed IMEI/IMSIs,to the MSDAVS 3103.

In step 37-6, the MSDAVS 3103 can forward this complete ESN/MIN list tothe Opt-in Database 3113. The Opt-in Database 3113 can cross-reference,or filter, this complete list of MIN/ESNs against the stored or archivedlist of subscribers, in a look-up table type functionality.

In step 37-7, the Opt-in Database 3113 can return the list of thesubscriber IMEI/IMSI telephone numbers to the MSDAVS 3103, determined bythe above cross-referencing or filtering.

In step 37-8, the MSDAVS 3103 can provide this filtered list ofsubscriber telephone numbers to the SAMBA-MSDAVS service 3223, whichthen can start providing the SAMBA service 2000 exclusively to theidentified subscribers. As described above in great detail, this SAMBAservice 2000 can involve sending messages, promotions, alerts ornotifications to the subscribers based on their location and theirpreviously identified interests, including gaming, financial, sports,traffic or any other types of interest. FIGS. 25 and 26 illustrate ingreat detail the SAMBA service, and any combination of the presentlydescribed SAMBA-MSDAVS System 3003 and the SAMBA embodiments of FIGS. 25and 26 can be implemented as well.

FIG. 38 illustrates a Community Notification MSDAVS System 3004. In someembodiments, a community may wish to implement mobile notificationsystems. Examples include campuses, where the administration or thepolice may wish to notify the students about an event of concern, suchhas a criminal activity. Or in other cases a county administration maywish to notify the residents of the county about an event of concern,such as a rapidly advancing fire or mudslide, necessitating the quickorganization of the resident's mobilization and movement patterns, suchas preferred or dis-preferred routes.

After learning about an event of concern, such as the above describedcriminal activity or natural catastrophe, a Mobile CommunityNotification Service (MCNS) 3224 may wish to notify the community itserves.

In step 38-1 the MCNS 3224 can request the telephone numbers of allcommunity members or residents within a Notification Area from theMSDAVS 3104. This Notification Area can be defined e.g. by the celltowers within this area, in which case the MCNS 3224 can request alltelephone numbers registered at cell towers within the NotificationArea.

In steps 38-2 and 38-3 the MSDAVS 3104 can communicate with the ServicePolicy Database 3124 regarding the proper procedure and policy for sucha process.

In the optional step 38-4, the MSDAVS 3104 can request the list of allcell towers within the Notification Area, as defined by the MCNS 3224,from a Cell Tower Database 3304-1.

In the corresponding optional step 38-5, the Cell Tower Database 3304-1can provide the list of cell towers in the Notification Area.

In step 38-6, the MSDAVS 3104 can request all the cell phone numbersregistered at the cell towers within the Notification Area from aTelephone Number Directory/SPID database 3304-2.

In step 38-7, the Telephone Number Directory/SPID database 3304-2 canreturn all phone numbers registered at the identified cell towers.

In some implementations, this Mobile Community Notification MSDAVSSystem 3004 can be opt-in based, in others it can be not opt-in based. Afeature of the of the non-opt-in based service is that all members ofthe community can be reached, if the event of concern truly requires it,such as the above mentioned dangerous criminal activity on a campus or arapidly advancing fire in a residential area. A feature of the opt-inbased system is that it can provide notification about events, which areimportant, but are of less pressing nature. Some implementations mayoffer both levels of access, and allow the operator of the MobileCommunity Notification Service 3224 to choose the level of theNotification. There can be various levels of the approval process togain the right to operate such a non-opt-in MCNS 3224, to make sure thatthe system is used properly.

In an opt-in based MCNS 3224 steps 38-8 and 38-9 can be performed, wherethe MSDAVS 3104 communicates with an Opt-in Database 3114 to filter thecomplete list of phone users in the Notification Area against an Opt-inDatabase to identify the subscribers in the Notification Area. Thisfiltered list can be returned in step 38-9 by the Opt-in Database 3114.

In a non-opt-in based MCNS 3224 steps 38-8 and 38-9 may not beperformed.

In step 38-10 the list of telephone numbers, either filtered ornon-filtered, can be forwarded to the Mobile Community NotificationService 3224, which in turn can start notifying the members in theNotification Area.

The above described Mobile Subscriber Detection Authorization andVerification Systems 3000-3004 can be organized according to numerousbusiness models. In systems, where the confidentiality of theinformation is highly valued, the MSDAVS 3100 and the MAPS 3200 can beseparate entities to ensure the required and expected confidentiality.In other systems, where other aspects are more highly prized, anycombination of the MSDAVS 3100, the MAPS 3200, and the ConfidentialInformation Owner 3300 can have various levels of businessrelationships, ranging from a contractual, through partially commonlyowned, to fully commonly owned relationships.

While the invention was described in relation to specific embodimentsonly, these descriptions should not be construed as limiting. On thecontrary, these embodiments were provided only by way of illustrations.Any combination of the above examples, any type of sub-combinations, andall types of inclusions of equivalent embodiments are within the scopeof the invention. The invention is only limited by the appended claims.

1-20. (canceled)
 21. A method comprising: receiving, on a central serverusing one or more processors, alert information, the alert informationincluding an alert location and an alert-information-related choice;selecting, using the one or more processors, a mobile device to receivean alert message based at least in part on the alert location;generating, using the one or more processors, the alert messageincluding at least a portion of the alert information including thealert-information-related choice; and sending, over a network using theone or more processors, the alert message to the mobile device.
 22. Themethod of claim 21, wherein the selecting the mobile device includescorrelating, using the one or more processors, location informationreceived from the mobile device with the alert location.
 23. The methodof claim 22, wherein the correlating the location information receivedfrom the mobile device with the alert location includes: generating,using the one or more processors, an event zone associated with thealert location, and determining, using the one or more processors,whether the location information received from the mobile deviceincludes a location within the event zone.
 24. The method of claim 21,wherein the generating the alert message includes selecting a hot key asa response to the alert-information-related choice, wherein the hot keyis selectable on the mobile device upon receipt of the alert message.25. The method of claim 21, wherein the generating the alert messageincludes associating a promotional offer with thealert-information-related choice.
 26. The method of claim 25, whereinthe associating the promotional offer includes linking one or morecontact references related to the promotional offer with thealert-information-related choice, wherein selecting thealert-information-related choice on the mobile device causes the mobiledevice to activate one of the one or more contact references.
 27. Themethod of claim 21, wherein the receiving alert information includesreceiving information about one or more of the following types ofevents: traffic incident; weather event; sporting event; recreationevent; and an emergency situation.
 28. The method of claim 21, whereingenerating the alert message includes generating: a first message partincluding information describing the event; a second message partincluding an alert-information-related choice; and a third message partincluding an event-information-related choice, wherein theevent-information-related choice is selected based at least in part oninformation included within the alert information.
 29. The method ofclaim 28, wherein generating the third message part includes selecting apromotional offer within a predefined proximity to the alert location.30. The method of claim 21, wherein receiving the alert informationincludes: aggregating alert information from a plurality of sources; andcorrelating location information included in the alert informationreceived from the plurality of sources to generate the alert informationassociated with a single event.
 31. An information alert systemcomprising: a central server including one or more processors and amemory device, the memory device including instructions that, whenexecuted by the one or more processors, cause the central server to:receive alert information including an alert location and analert-information-related choice; select a mobile device to receive analert message based at least in part on the alert location; generate thealert message including at least a portion of the alert informationincluding the alert-information-related choice; and send the alertmessage to the mobile device.
 32. The information alert system of claim31, wherein the instructions that cause the server to select the mobiledevice further include instructions that cause the server to correlatelocation information received from the mobile device with the alertlocation.
 33. The information alert system of claim 32, wherein theinstructions that cause the server to correlate the location informationreceived from the mobile device with the alert location further includeinstructions that cause the server to: generate an event zone associatedwith the alert location, and determine whether the location informationreceived from the mobile device includes a location within the eventzone.
 34. The information alert system of claim 31, wherein theinstructions that cause the server to generate the alert message furtherinclude instructions that cause the server to select a hot key as aresponse to the alert-information-related choice, wherein the hot key isselectable on the mobile device upon receipt of the alert message. 35.The information alert system of claim 31, wherein the instructions thatcause the server to generate the alert message further includeinstructions that cause the server to associate a promotional offer withthe alert-information-related choice.
 36. The information alert systemof claim 35, wherein the instructions that cause the server to associatethe promotional offer further include instructions that cause the serverto link one or more contact references related to the promotional offerwith the alert-information-related choice, wherein selecting thealert-information-related choice on the mobile device causes the mobiledevice to activate one of the one or more contact references.
 37. Theinformation alert system of claim 31, wherein the instructions thatcause the server to receive alert information further includeinstructions that cause the server to receive information about one ormore of the following types of events: traffic incident; weather event;sporting event; recreation event; and an emergency situation.
 38. Theinformation alert system of claim 31, wherein instructions that causethe server to generate the alert message further include instructionsthat cause the server to generate: a first message part includinginformation describing the event; a second message part including analert-information-related choice; and a third message part including anevent-information-related choice, wherein the event-information-relatedchoice is selected based at least in part on information included withinthe alert information.
 39. The information alert system of claim 38,wherein instructions that cause the server to generate the third messagepart further include instructions that cause the server to select apromotional offer within a predefined proximity to the alert location.40. The information alert system of claim 31, wherein instructions thatcause the server to receive the alert information further includeinstructions that cause the server to: aggregate alert information froma plurality of sources; and correlate location information included inthe alert information received from the plurality of sources to generatethe alert information associated with a single event.
 41. Amachine-readable storage medium including instructions that, whenexecuted on a machine, cause the machine to: receive alert informationabout an event from multiple sources, the alert information including anevent location and an event-information-related choice; aggregate thealert information received from multiple sources to identify a singleevent location and a single event-information-related choice; select aplurality of mobile devices to receive an alert message based at leastin part on the single event location; generate the alert messageincluding at least a portion of the alert information including thesingle event-information-related choice; and send the alert message tothe plurality of mobile devices.